darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2024-11-29 15:00:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Make it clear what should be done with patches to the top level configure files

Browse Source 
(other than config.guess and config.sub).
Add binutils@sources.redhat.com as an address to which patches can be sent.
This commit is contained in:
Nick Clifton 2003-09-04 12:30:27 +00:00
parent 8ad30312ff
commit 04fbe4296a
2 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
binutils/ChangeLog
View File

@ -1,3 +1,10 @@
2003-09-04 Nick Clifton <nickc@redhat.com>
* MAINTAINERS: Make it clear what should be done with patches to
the top level configure files (other than config.guess and
config.sub). Add binutils@sources.redhat.com as an address to
which patches can be sent.
2003-09-04 Nick Clifton <nickc@redhat.com>
* readelf.c (get_machine_flags): Recognise V850E1 machine type.

10
binutils/MAINTAINERS
View File

@ -14,14 +14,18 @@ The home page for binutils is:
and patches should be sent to:
bug-binutils@gnu.org
bug-binutils@gnu.org or binutils@sources.redhat.com
with "[Patch]" as part of the subject line. Note - patches to the
top level configure.in and config.sub scripts should be sent to:
top level config.guess and config.sub scripts should be sent to:
config-patches@gnu.org
and not to the binutils list.
and not to the binutils lists. Patches to the other top level
configure files (configure, configure.in, config-if, config-ml.in)
should be sent to the binutils lists, and copied to the gcc and gdb
lists as well (gcc-patches@gcc.gnu.org and
gdb-patches@sources.redhat.com).
--------- Blanket Write Privs ---------