* jv-exp.y (insert_exp): Define using ISO syntax.

[deliverable/binutils-gdb.git] / MAINTAINERS

diff --git a/MAINTAINERS b/MAINTAINERS
index b2077e7c26a1e262461dea797d3cd5ea9c02dc22..3c2c6f111866b48ac6a2b3ef518d4ca5ac113224 100644 (file)
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4,7 +4,7 @@ Please do not make ChangeLog entries.
 COPYING, COPYING.LIB, README
        http://gnu.org.
 
 COPYING, COPYING.LIB, README
        http://gnu.org.
 

-Makefile.*; configure; configure.in; src-release
+Makefile.*; configure; configure.ac; 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
        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


@@ -13,7 +13,9 @@ Makefile.*; configure; configure.in; src-release
                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 
                binutils@sources.redhat.com
                gdb-patches@sources.redhat.com
 

-bfd/; binutils/; gas/; gprof/; ld/; opcodes/; cpu/; BFD's part of include/
+bfd/; binutils/; elfcpp/; gas/; gold/; 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:
        binutils: http://sources.redhat.com/binutils/
        Patches to binutils@sources.redhat.com.
        Please notify the following of any interface changes:


@@ -47,15 +49,19 @@ 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.
+
+libdecnumber/
+       See libiberty.  The master copy of this directory is in the GCC
+       repository.

 
 ltconfig; ltmain.sh; ltcf-*.sh
        libtool: http://www.gnu.org/software/libtool/
 
 ltconfig; ltmain.sh; ltcf-*.sh
        libtool: http://www.gnu.org/software/libtool/


@@ -99,7 +105,7 @@ winsup/
        See also winsup/MAINTAINERS.
 
 config-ml.in; makefile.vms; mkdep; setup.com;
        See also winsup/MAINTAINERS.
 
 config-ml.in; makefile.vms; mkdep; setup.com;

-etc/; intl/; utils/;
+etc/; utils/;

        Any global maintainer can approve changes to these
        files and directories.
 
        Any global maintainer can approve changes to these
        files and directories.