Change sources over to using GPLv3

[deliverable/binutils-gdb.git] / MAINTAINERS

diff --git a/MAINTAINERS b/MAINTAINERS
index 519bafdbd940b4d72dffc21696dbd706ba889652..6c5f732805e9fcd60d5ebd617ec920b8f0ddd627 100644 (file)
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5,7 +5,11 @@ COPYING, COPYING.LIB, README
        http://gnu.org.
 
 Makefile.*; configure; configure.in; src-release
        http://gnu.org.
 
 Makefile.*; configure; configure.in; src-release

-       Please notify the following of any committed patches.
+       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:

                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 
                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 


@@ -43,15 +47,15 @@ gdb/; readline/; sim/; GDB's part of include/
 include/
        See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
 
 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
        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.
+       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/
 
 ltconfig; ltmain.sh; ltcf-*.sh
        libtool: http://www.gnu.org/software/libtool/


@@ -94,9 +98,17 @@ winsup/
        General discussion cygwin@sources.redhat.com.
        See also winsup/MAINTAINERS.
 
        General discussion cygwin@sources.redhat.com.
        See also winsup/MAINTAINERS.
 

-config-ml.in; setup.com; missing; makefile.vms; utils/; config/;
-makefile.vms; missing; ylwrap; mkdep; etc/; install-sh; intl/
-       Ask DJ Delorie <dj@redhat.com> after reading the libiberty entry.
+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
 
 modules file
        Obviously changes to this file should not go through