gas/

[deliverable/binutils-gdb.git] / MAINTAINERS

diff --git a/MAINTAINERS b/MAINTAINERS
index 104b8154b9c2e8d76953c8a17a0e60de72dc30bd..b2077e7c26a1e262461dea797d3cd5ea9c02dc22 100644 (file)
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4,12 +4,16 @@ Please do not make ChangeLog entries.
 COPYING, COPYING.LIB, README
        http://gnu.org.
 
 COPYING, COPYING.LIB, README
        http://gnu.org.
 

-Makefile.in; configure; configure.in
-       Please notify the following of any committed patches.
+Makefile.*; configure; configure.in; src-release
+       Any global maintainer can approve changes to these
+       files, but they should be aware that they need to
+       be kept in sync with their counterparts in the GCC
+       repository.  Also please notify the following of
+       any committed patches:

                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 
                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 

-bfd/; binutils/; gas/; gprof/; ld/; opcodes/; BFD's part of include/
+bfd/; binutils/; gas/; gprof/; ld/; opcodes/; cpu/; BFD's part of include/

        binutils: http://sources.redhat.com/binutils/
        Patches to binutils@sources.redhat.com.
        Please notify the following of any interface changes:
        binutils: http://sources.redhat.com/binutils/
        Patches to binutils@sources.redhat.com.
        Please notify the following of any interface changes:


@@ -21,29 +25,24 @@ cgen/; cgen parts of opcodes/, sim/ & include/
        May need separate opcodes/ or sim/ approval for
                commits of regenerated files there.
 
        May need separate opcodes/ or sim/ approval for
                commits of regenerated files there.
 

-config.guess; config.sub; dejagnu/config.guess;
-readline/support/config.sub; readline/support/config.guess
+config.guess; config.sub; readline/support/config.{sub,guess}

        config: http://savannah.gnu.org/projects/config
        Patches to config-patches@gnu.org.
        Changes need to be done in tandem with the official CONFIG
        sources or submitted to the master file maintainer and brought
        config: http://savannah.gnu.org/projects/config
        Patches to config-patches@gnu.org.
        Changes need to be done in tandem with the official CONFIG
        sources or submitted to the master file maintainer and brought

-       in via a merge.
+       in via a merge.  When updating any of these files, please be
+       sure to update all of them.

        Please notify the following of any committed patches:
                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 
        Please notify the following of any committed patches:
                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 

-dejagnu/
-       Send all patches to:
-       http://www.gnu.org/software/dejagnu/
-       mail:bug-dejagnu@gnu.org
-       For changes to the local repostory, send them to
-       gdb-patches@sources.redhat.com when generic; and sid@,
-       binutils@, gcc@, etc. for sub-components.
+depcomp
+        Send bug reports and patches to bug-automake@gnu.org.

 
 

-gdb/; mmalloc/; readline/; sim/; GDB's part of include/ & dejagnu/
-       gdb: http://sources.redhat.com/gdb/
+gdb/; readline/; sim/; GDB's part of include/
+       GDB: http://www.gnu.org/software/gdb/

        Patches to gdb-patches@sources.redhat.com.
        Patches to gdb-patches@sources.redhat.com.

-       See also gdb/MAINTAINERS, sim/MAINTAINERS, mmalloc/MAINTAINERS.
+       See also gdb/MAINTAINERS and sim/MAINTAINERS.

 
 include/
        See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
 
 include/
        See binutils/, gdb/, sid/, gcc/, libiberty/ etc.


@@ -58,8 +57,8 @@ libiberty/; libiberty's part of include/
        Otherwise, changes are automatically merged, usually within
        a day.
 
        Otherwise, changes are automatically merged, usually within
        a day.
 

-ltconfig; ltmain.sh
-       libtool: http://gnu.org
+ltconfig; ltmain.sh; ltcf-*.sh
+       libtool: http://www.gnu.org/software/libtool/

        Changes need to be done in tandem with the official LIBTOOL
        sources or submitted to the master file maintainer and brought
        in via a merge.
        Changes need to be done in tandem with the official LIBTOOL
        sources or submitted to the master file maintainer and brought
        in via a merge.


@@ -79,7 +78,7 @@ newlib/; libgloss/
        http://sources.redhat.com/newlib/
        Patches to newlib@sources.redhat.com.
 
        http://sources.redhat.com/newlib/
        Patches to newlib@sources.redhat.com.
 

-sid/; SID's part of cgen/ & dejagnu/
+sid/; SID's part of cgen/

        sid: http://sources.redhat.com/sid/
        Patches to sid@sources.redhat.com
 
        sid: http://sources.redhat.com/sid/
        Patches to sid@sources.redhat.com
 


@@ -99,11 +98,17 @@ winsup/
        General discussion cygwin@sources.redhat.com.
        See also winsup/MAINTAINERS.
 
        General discussion cygwin@sources.redhat.com.
        See also winsup/MAINTAINERS.
 

-expect/; config-ml.in; mpw-README; mpw-build.in; mpw-config.in;
-mpw-configure; mpw-install; setup.com; missing; makefile.vms; utils/;
-config/; config.if; makefile.vms; missing; ylwrap; mkdep; etc/;
-install-sh; intl/
-       Ask DJ Delorie <dj@redhat.com> after reading the libiberty entry.
+config-ml.in; makefile.vms; mkdep; setup.com;
+etc/; intl/; utils/;
+       Any global maintainer can approve changes to these
+       files and directories.
+
+compile; depcomp; install-sh; missing; ylwrap;
+config/
+       Any global maintainer can approve changes to these
+       files and directories, but they should be aware
+       that they need to be kept in sync with their
+       counterparts in the GCC repository.

 
 modules file
        Obviously changes to this file should not go through
 
 modules file
        Obviously changes to this file should not go through