From d7ce6bd337e14c5d92e68dabdf6e52966072d299 Mon Sep 17 00:00:00 2001 From: "Andreas K. Hüttel" Date: Tue, 19 May 2020 23:33:48 +0300 Subject: Add files from Gentoo binutils repo, tag gentoo/binutils-9999-6 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Andreas K. Hüttel --- README.Gentoo.patches | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 README.Gentoo.patches (limited to 'README.Gentoo.patches') diff --git a/README.Gentoo.patches b/README.Gentoo.patches new file mode 100644 index 0000000..504dc67 --- /dev/null +++ b/README.Gentoo.patches @@ -0,0 +1,31 @@ + ============ + === What === + ============ + +Gentoo patchsets for binutils are maintained as vendor branches of the upstream +binutils-glb 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/binutils-gdb + + =========== + === How === + =========== + +The patch naming convention is precisely as generated by "git format-patch". + +All patches should apply with -p1 (so they can be used both with the legacy +epatch function and the new, more strict eapply function). + +Commits where the commit message starts with "[no patch]" will not be included +in the patch tarball. This is useful for changes to the tarball generation +script, or for the addition of extra files that are not patches. -- cgit v1.2.3-65-gdbad