 ================
 === W[hat]TF ===
 ================

Gentoo patchsets that have grown too large to keep on the rsync mirrors have 
been moved to our git tree.  From there, we bundle up all the whee little 
patches into a tarball and distribute it via our public mirroring system.

If you want specific info about a patch (like wtf it does or whose great idea 
it was to change the code), read the patch! We try to fill out the top of 
them with useful info such as what it does, why it's needed, bug reports, 
original creators, etc...  For simple patches, we reserve the right to assume 
your IQ is greater than absolute 0 and figure out what it does w/out an 
explanation.  If, by some miracle of science, it falls below the absolute 0 
mark, you should help mankind by finding some scientists and letting them 
probe you with their ... erm ... probes.

 =================
 === W[here]TF ===
 =================

You can usually find these patches as xz compressed tarball at
https://dev.gentoo.org/~polynomial-c

 ===============
 === H[ow]TF ===
 ===============

The patch naming/applying convention might be a little confusing to the Gentoo
outsider, so here's a quick rundown. Patch tarballs are applied in Gentoo via
a helper command called "eapply".

The patch naming convention is part rigorous and part open ended. By default,
the patch should follow:
	#_<arch>_<desc>.patch
The number field is to provide strict numerical ordering and has no limit (well,
except for your IMAGINATION).  The <arch> field corresponds to the Gentoo arch
naming convention (so expect to see "amd64" instead of "x86_64").  If you see
"all" (which is how we strongly encourage people to manage things), then the
patch should be applied for all arches, and any arch-specific issues can then
be handled at build time (configure detection or something).  The <desc> is a
free form field where people can stick whatever they want.
