2001-03-20 Michael Chastain <chastain@redhat.com>

[deliverable/binutils-gdb.git] / binutils / MAINTAINERS

diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS
index 4a72c7507f99c253829894ade1ea79e7b3211ed1..6f66f4c0a8b9818a616b8abcde9d4e0303f48446 100644 (file)
--- a/binutils/MAINTAINERS
+++ b/binutils/MAINTAINERS
@@ -6,6 +6,9 @@ gas, gprof, ld, and opcodes subdirectories.  The home page for binutils
 is http://sources.redhat.com/binutils/ and patches should be sent to
 binutils@sources.redhat.com with "[patch]" as part of the subject.
 
+Note - patches to the top level configure.in and config.sub scripts
+should be sent to config-patches@gnu.org and not to the binutils list.
+
                --------- Blanket Write Privs ---------
 
 Nick Clifton <nickc@redhat.com> (head maintainer)
@@ -39,6 +42,7 @@ i860          Jason Eckhardt <jle@redhat.com>
 ix86           Alan Modra <alan@linuxcare.com.au>
 ix86 COFF,PE   DJ Delorie <dj@redhat.com>
 ix86           H.J.Lu <hjl@gnu.org>
+ix86 INTEL MODE Diego Novillo <dnovillo@redhat.com>
 MN10300                Eric Christopher <echristo@redhat.com>
 MIPS           Ulf Carlsson <ulfc@calypso.engr.sgi.com>
 PPC            Geoff Keating <geoffk@redhat.com>
@@ -46,6 +50,9 @@ SH            J
 SH             Hans-Peter Nilsson <hp@bitrange.com>
 SPARC          Jakub Jelinek <jakub@redhat.com>
 68HC11 68HC12   Stephane Carrez <Stephane.Carrez@worldnet.fr>
+DWARF2         Jason Merrill <jason@redhat.com>
+x86_64         Jan Hubicka <jh@suse.cz>
+x86_64         Andreas Jaeger <aj@suse.de>
 
                --------- CGEN Maintainers -------------
 
@@ -72,3 +79,14 @@ one of the above lists (blanket write or maintainers).
 [It's a huge list, folks.  You know who you are.  If you have the
  *ability* to do binutils checkins, you're in this group.  Just remember
  to get approval before checking anything in.]
+
+              -------------  Obvious Fixes -------------
+
+Fixes for obvious mistakes do not need approval, and can be checked in
+right away, but the patch should still be sent to the binutils list.
+The definition of obvious is a bit hazy, and if you are not sure, then
+you should seek approval first.  Obvious fixes include fixes for
+spelling mistakes, blatantly incorrect code (where the correct code is
+also blatantly obvious), and so on.  Obvious fixes should always be
+small, the larger they are, the more likely it is that they contain
+some un-obvious side effect or consequence.