X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=MAINTAINERS;h=b09fbc0ea7c229eac5826982d388501137840611;hb=68ffd9368a020fb685520da51f8c672c720869e4;hp=046c5ea8246799b1161dc2c4a36f03736532ca2b;hpb=dcb5e50678a5b4e3cc1453bbd8a9cc1165ed0c8d;p=external%2Fbinutils.git

diff --git a/MAINTAINERS b/MAINTAINERS
index 046c5ea..b09fbc0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -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
@@ -104,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