Automatic date update in version.in

[thirdparty/binutils-gdb.git] / MAINTAINERS

diff --git a/MAINTAINERS b/MAINTAINERS
index a471c907eef642010aa31d7a25617b9f1cd567b3..5b8a4efbdf69866245c0ff7b24d8d3aa84ca2104 100644 (file)
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14,7 +14,7 @@ Makefile.*; configure; configure.ac; src-release
                gdb-patches@sourceware.org
 
 bfd/; binutils/; elfcpp/; gas/; gold/; gprof/; ld/; opcodes/; cpu/;
-BFD's part of include/
+libctf/; BFD's and libctf's parts of include/
 
        binutils: http://sourceware.org/binutils/
        Patches to binutils@sourceware.org.
@@ -38,18 +38,22 @@ config.guess; config.sub; readline/support/config.{sub,guess}
                binutils@sourceware.org
                gdb-patches@sourceware.org
 
-depcomp
+depcomp; mkinstalldirs
         Send bug reports and patches to bug-automake@gnu.org.
 
-gdb/; readline/; sim/; GDB's part of include/
+gdb/; gdbserver/; gdbsupport/; gnulib/; readline/; sim/; GDB's part of include/
        GDB: http://www.gnu.org/software/gdb/
        Patches to gdb-patches@sourceware.org.
        See also gdb/MAINTAINERS and sim/MAINTAINERS.
 
 include/
-       See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
+       The rule is that if the file exists in the gcc tree
+       then gcc owns it.  Thus you have to look at the gcc tree
+       to know whether any particular file is owned by gcc.
+       See also binutils/, gdb/, sid/, gcc/, libiberty/ etc.
 
-intl/; config.rhost; libiberty/; libiberty's part of include/ 
+intl/; config.rhost; libiberty/; libiberty's part of include/;
+compile; depcomp; install-sh; missing; ylwrap; config/
        gcc: http://gcc.gnu.org
        Changes need to be done in tandem with the official GCC
        sources or submitted to the master file maintainer and brought
@@ -69,12 +73,8 @@ ltconfig; ltmain.sh; ltcf-*.sh
        sources or submitted to the master file maintainer and brought
        in via a merge.
 
-mkinstalldirs; move-if-change
-       autoconf: http://gnu.org
-       Patches to autoconf-patches@gnu.org.
-       Changes need to be done in tandem with the official AUTOCONF
-       sources or submitted to the master file maintainer and brought
-       in via a merge.
+move-if-change
+       Send bug reports and patches to bug-gnulib@gnu.org.
 
 symlink-tree
        gcc: http://gcc.gnu.org
@@ -108,13 +108,6 @@ etc/; 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
        If you understand the file format (or can cut-and-paste existing
        entries), modify it. If it scares you, get someone who does