summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2012-05-12 03:10:17 +0000
committerMike Frysinger <vapier@gentoo.org>2012-05-12 03:10:17 +0000
commit9eb322aa05881f61062a67c60b909366e27aa1f9 (patch)
treeb3bb9b4cecd63337aeb3b5c155a3c5ca927d3678 /MAINTAINERS
parent7dbe414f2453b79231a1a8ab5ce957a28a04628c (diff)
downloadbinutils-gdb-9eb322aa05881f61062a67c60b909366e27aa1f9.tar.gz
MAINTAINERS: clarify policy with config/ (and other top level files)
Rather than copy & paste more text, just merge the existing config/ section with the existing intl/ section. This ends up clarifying the policy with that subdir (and top level files) that any commit made to gcc's repo is allowed to be merged with the sourceware tree without pre-approval. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'MAINTAINERS')
-rw-r--r--MAINTAINERS10
1 files changed, 2 insertions, 8 deletions
diff --git a/MAINTAINERS b/MAINTAINERS
index 046c5ea8246..dd8601b4ff7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -49,7 +49,8 @@ gdb/; readline/; sim/; GDB's part of include/
include/
See 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 +105,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