diff options
Diffstat (limited to 'scripts/gentoo/README.Gentoo.patches')
| -rw-r--r-- | scripts/gentoo/README.Gentoo.patches | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/scripts/gentoo/README.Gentoo.patches b/scripts/gentoo/README.Gentoo.patches new file mode 100644 index 0000000000..8e9777238d --- /dev/null +++ b/scripts/gentoo/README.Gentoo.patches @@ -0,0 +1,35 @@ + ============ + === What === + ============ + +Gentoo patchsets for glibc are maintained as vendor branches of the upstream +glibc git repository. From there, we bundle all the commits into a tarball +and distribute it via our public mirroring system. + +If you want specific info about a patch (like what it does or whose great idea +it was to change the code), read the patch! We try to fill out the commit +messages with useful info such as what it does, why it's needed, bug reports, +original creators, etc... + + ============= + === Where === + ============= + +Currently, https://github.com/gentoo/glibc + + =========== + === How === + =========== + +For historical reasons, the patch naming convention is slightly different +from Git. When "git format-patch" generates a patch file of the name + xxxx-commit-message.patch +it is placed into the tarball as + xxxx_all_commit-message.patch + +This signifies that the patch should be applied on all Gentoo "arches". +In the past also patches were included that should be applied only on one +specific arch (say, hppa). We're trying hard to avoid that in the future. + +All patches should apply with -p1 (so they can be used both with the legacy +epatch function and the new, more strict eapply function). |