summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDJ Delorie <dj@delorie.com>2001-07-26 14:20:05 +0000
committerDJ Delorie <dj@delorie.com>2001-07-26 14:20:05 +0000
commit893a2991fbc5bc32a2209d2a6136fbb1b25586d0 (patch)
tree07c4d5debcb2ef7f5909cc5628f326041aa23cc3
parent641eaa7aaf5d5534d0fd779555e33181ae9f648e (diff)
downloadgdb-893a2991fbc5bc32a2209d2a6136fbb1b25586d0.tar.gz
* MAINTAINERS: Clarify libiberty merge rules and procedures.
-rw-r--r--ChangeLog4
-rw-r--r--MAINTAINERS6
2 files changed, 9 insertions, 1 deletions
diff --git a/ChangeLog b/ChangeLog
index cf1c3d94355..2fdc15d2733 100644
--- 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 2201a923ad9..b3e04387a44 100644
--- 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