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:
-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/
Please notify the following of any interface changes:
-cgen/, cgen parts of opcodes/, sim/, include/
+cgen/; cgen parts of opcodes/, sim/ & include/
cgen: http://sources.redhat.com/cgen/
May need separate opcodes/ or sim/ approval for
commits of regenerated files there.
-config.guess, config.sub
- config: http://gnu.org
+config.guess; config.sub; readline/support/config.{sub,guess}
+ config: http://savannah.gnu.org/projects/config
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:
+
+depcomp
+
+gdb/; readline/; sim/; GDB's part of include/
+ GDB: http://www.gnu.org/software/gdb/
+ See also gdb/MAINTAINERS and sim/MAINTAINERS.
-libiberty/ & libiberty's part of include/
+include/
+ See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
+
+intl/; config.rhost; libiberty/; libiberty's part of include/
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
- in via a merge.
-
-ltconfig, ltmain.sh
- libtool: http://gnu.org
+ in via a merge. Note: approved patches in gcc's libiberty or
+ intl are automatically approved in this libiberty and intl also;
+ feel free to merge them yourself if needed sooner than the next
+ merge. Otherwise, changes are automatically merged, usually
+ within a day.
+
+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.
-mkinstalldirs, move-if-change, symlink-tree
+mkinstalldirs; move-if-change
autoconf: http://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.
-newlib/, libgloss/
+symlink-tree
+ gcc: http://gcc.gnu.org
+ See libiberty.
+
+newlib/; libgloss/
http://sources.redhat.com/newlib/
-gdb/, mmalloc/, readline/, sim/ & GDB's part of include/
- gdb: http://sources.redhat.com/gdb/
- See also gdb/MAINTAINERS, sim/MAINTAINERS, mmalloc/MAINTAINERS.
+sid/; SID's part of cgen/
+ sid: http://sources.redhat.com/sid/
-itcl/, tcl/, tix/, tk/, libgui/
+texinfo/texinfo.tex
+ texinfo: http://ftp.gnu.org.
+ Latest version can be found on ftp://ftp.gnu.org and can be
+ imported at any (reasonable) time.
+ Please not use GCC's texinfo. Please do not import texinfo.
+
+tcl/; tix/; itcl/; tk/; libgui/
insight: http://sources.redhat.com/insight/
See also winsup/MAINTAINERS.
-texinfo/texinfo.tex
- texinfo: http://ftp.gnu.org.
- Latest version can be found on ftp://ftp.gnu.org and can be
- imported at any (reasonable) time.
- Please not use GCC's texinfo. Please do not import texinfo.
-
-expect/, dejagnu/, 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/
- ?
+config-ml.in; makefile.vms; mkdep; setup.com;
+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
Obviously changes to this file should not go through