summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2020-05-13 10:56:28 +0300
committerAndreas K. Hüttel <dilfridge@gentoo.org>2020-05-13 11:03:56 +0300
commitfbd0918c2d6531cafeab6eb83d0a45dab997f8fb (patch)
treeb32de69cfdb6da83e869c38c19ac7068b5390a93 /README.Gentoo.patches
downloadglibc-patches-fbd0918c2d6531cafeab6eb83d0a45dab997f8fb.tar.gz
glibc-patches-fbd0918c2d6531cafeab6eb83d0a45dab997f8fb.tar.bz2
glibc-patches-fbd0918c2d6531cafeab6eb83d0a45dab997f8fb.zip
Copy exact files from glibc repo, tag gentoo/glibc-9999-17
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
Diffstat (limited to 'README.Gentoo.patches')
-rw-r--r--README.Gentoo.patches26
1 files changed, 26 insertions, 0 deletions
diff --git a/README.Gentoo.patches b/README.Gentoo.patches
new file mode 100644
index 0000000..c6f94dc
--- /dev/null
+++ b/README.Gentoo.patches
@@ -0,0 +1,26 @@
+ ============
+ === 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 ===
+ ===========
+
+Patches are named exactly as generated by "git format-patch".
+All patches thus apply with -p1 (so they can be used both with the legacy
+epatch function and the new, more strict eapply function).