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:
May need separate opcodes/ or sim/ approval for
commits of regenerated files there.
-config.guess; config.sub; dejagnu/config.guess; dejagnu/config.sub;
-readline/support/config.sub; readline/support/config.guess
+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
-dejagnu/
- Send all patches to:
- http://www.gnu.org/software/dejagnu/
- For changes to the local repostory, send them to
- binutils@, gcc@, etc. for sub-components.
+depcomp
-gdb/; mmalloc/; readline/; sim/; GDB's part of include/ & dejagnu/
- gdb: http://sources.redhat.com/gdb/
+gdb/; readline/; sim/; GDB's part of include/
+ GDB: http://www.gnu.org/software/gdb/
- See also gdb/MAINTAINERS, sim/MAINTAINERS, mmalloc/MAINTAINERS.
+ See also gdb/MAINTAINERS and sim/MAINTAINERS.
include/
See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
-libiberty/; libiberty's part of include/
+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. Note: approved patches in gcc's libiberty
- are automatically approved in this libiberty 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
- 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.
http://sources.redhat.com/newlib/
-sid/; SID's part of cgen/ & dejagnu/
+sid/; SID's part of cgen/
sid: http://sources.redhat.com/sid/
See also winsup/MAINTAINERS.
-expect/; 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