X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=MAINTAINERS;h=b09fbc0ea7c229eac5826982d388501137840611;hb=0f407ee9f45d704dfed7207f2e2122cfa197ff70;hp=a471c907eef642010aa31d7a25617b9f1cd567b3;hpb=bf1102165389c7168c446ce3dcc209046372d599;p=deliverable%2Fbinutils-gdb.git

diff --git a/MAINTAINERS b/MAINTAINERS
index a471c907ee..b09fbc0ea7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -38,7 +38,7 @@ 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/
@@ -47,9 +47,13 @@ gdb/; readline/; sim/; GDB's part of include/
 	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