COPYING, COPYING.LIB, README
http://gnu.org.
-Makefile.in; configure; configure.in
+Makefile.in; configure; configure.in; src-release
Please notify the following of any committed patches.
binutils@sources.redhat.com
gdb-patches@sources.redhat.com
-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/
Patches to binutils@sources.redhat.com.
Please notify the following of any interface changes:
May need separate opcodes/ or sim/ approval for
commits of regenerated files there.
-config.guess; config.sub; dejagnu/config.guess;
+config.guess; config.sub; dejagnu/config.guess; dejagnu/config.sub;
readline/support/config.sub; readline/support/config.guess
- config: http://gnu.org
+ config: http://savannah.gnu.org/projects/config
Patches to config-patches@gnu.org.
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:
+ binutils@sources.redhat.com
+ gdb-patches@sources.redhat.com
dejagnu/
- Notify http://dejagnu.sourceforge.net/ of generic changes.
- Generic patches to gdb-patches@sources.redhat.com;
- Other dependents of dejagnu include sid@, binutils@, gcc@, etc.
+ dejagnu: http://www.gnu.org/software/dejagnu/
+ Patches to bug-dejagnu@gnu.org
+ Avoid making changes to the local repository; please send
+ patches upstream. Important and approved patches can be
+ checked into the src repository, otheriwse patches will be
+ imported from the next release.
gdb/; mmalloc/; readline/; sim/; GDB's part of include/ & dejagnu/
gdb: http://sources.redhat.com/gdb/
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
+ 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; 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
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.
+symlink-tree
+ gcc: http://gcc.gnu.org
+ See libiberty.
+
newlib/; libgloss/
http://sources.redhat.com/newlib/
Patches to newlib@sources.redhat.com.
General discussion cygwin@sources.redhat.com.
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/;
+expect/; config-ml.in; setup.com; missing; makefile.vms; utils/;
config/; config.if; makefile.vms; missing; ylwrap; mkdep; etc/;
install-sh; intl/
- Ask.
+ Ask DJ Delorie <dj@redhat.com> after reading the libiberty entry.
modules file
Obviously changes to this file should not go through