* MAINTAINERS: Clarify libiberty merge rules and procedures.

diff --git a/ChangeLog b/ChangeLog
index cf1c3d94355f7c5d20b7199703bb019708f9e7c3..2fdc15d2733dd57756df130048d53dc66da02c5a 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2001-07-26  DJ Delorie  <dj@redhat.com>
+
+       * MAINTAINERS: Clarify libiberty merge rules and procedures.
+
 2001-06-19  Alan Modra  <amodra@bigpond.net.au>
 
        * Makefile.in: Revert 2001-06-17.

diff --git a/MAINTAINERS b/MAINTAINERS
index 2201a923ad9e7a831e12a95cc0ec359f378069a5..b3e04387a4454d1c2643e037cebfe61c340b09e9 100644 (file)
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -46,7 +46,11 @@ 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.
+       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