This is the list of individuals responsible for maintenance and update
of the "binutils" module, which includes the bfd, binutils, include,
gas, gprof, ld, and opcodes subdirectories. The home page for binutils
-is http://sourceware.cygnus.com/binutils/ and patches should be sent to
-binutils@sourceware.cygnus.com with "[patch]" as part of the subject.
+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 ---------
AVR Denis Chertykov <denisc@overta.ru>
CRIS Hans-Peter Nilsson <hp@axis.com>
HPPA elf32 Alan Modra <alan@linuxcare.com.au>
+IA64 Jim Wilson <wilson@redhat.com>
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>
+SH Jörn Rennecke <amylaar@redhat.com>
+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 -------------
-CGEN is a tool for building, amounst other things, assemblers,
+CGEN is a tool for building, amongst other things, assemblers,
disassemblers and simulators from a single description of a CPU. It
creates files in several of the binutils directories, but it is
mentioned here since there is a single group that maintains CGEN and
[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.