RC tarballs and patches starting with 4.12-rc1

Why not provide these at their old locations?

We intentionally did not provide these automatically generated tarballs
and patches in locations previously used by Linus
(/pub/linux/kernel/v4.x/testing), even if this meant potentially
breaking automated scripts relying on contents published there. Anything
placed in the /pub tree is signed and curated directly by developers
and all patches and software archives published there invariably come
with a PGP signature provided directly by the developer of that software
(or one of the developers).

Patches and tarballs automatically generated by git.kernel.org are NOT
a replacement for this stringent process, but merely a convenience
service that comes with very different trust implications. By providing
these at different URLs we wanted all users of these services to make a
conscious decision on whether they want to trust these automatically
generated tarballs and patches, or whether they want to change their
process to continue to use PGP-verifiable tags directly from the git
tree.