binutils/MAINTAINERS

   1                 ========= Binutils Maintainers =========
   2
   3 This is the list of individuals responsible for maintenance and update
   4 of the "binutils" module, which includes the bfd, binutils, include,
   5 gas, gprof, ld, and opcodes subdirectories.  The home page for binutils
   6 is http://sources.redhat.com/binutils/ and patches should be sent to
   7 binutils@sources.redhat.com with "[patch]" as part of the subject.
   8
   9 Note - patches to the top level configure.in and config.sub scripts
  10 should be sent to config-patches@gnu.org and not to the binutils list.
  11
  12                 --------- Blanket Write Privs ---------
  13
  14 Nick Clifton <nickc@redhat.com> (head maintainer)
  15 Richard Henderson <rth@redhat.com>
  16 Ian Taylor <ian@zembu.com>
  17 Jeff Law <law@redhat.com>
  18 Jim Wilson <wilson@redhat.com>
  19 DJ Delorie <dj@redhat.com>
  20 Alan Modra <amodra@one.net.au>
  21 Michael Meissner <meissner@redhat.com>
  22
  23                     --------- Maintainers ---------
  24
  25 Maintainers are individuals who are responsible for, and have permission
  26 to check in changes in, certain subsets of the code.  Note that
  27 maintainers still need approval to check in changes outside of the
  28 immediate domain that they maintain.
  29
  30 If there is no maintainer for a given domain then the responsibility
  31 falls to the head maintainer (above).  If there are several maintainers
  32 for a given domain then responsibility falls to the first maintainer.
  33 The first maintainer is free to devolve that responsibility among the
  34 other maintainers.
  35
  36 ARM             Nick Clifton <nickc@redhat.com>
  37 AVR             Denis Chertykov <denisc@overta.ru>
  38 CRIS            Hans-Peter Nilsson <hp@axis.com>
  39 HPPA elf32      Alan Modra <amodra@one.net.au>
  40 IA64            Jim Wilson <wilson@redhat.com>
  41 i860            Jason Eckhardt <jle@redhat.com>
  42 ix86            Alan Modra <amodra@one.net.au>
  43 ix86 COFF,PE    DJ Delorie <dj@redhat.com>
  44 ix86            H.J.Lu <hjl@gnu.org>
  45 ix86 INTEL MODE Diego Novillo <dnovillo@redhat.com>
  46 MN10300         Eric Christopher <echristo@redhat.com>
  47 MIPS            Ulf Carlsson <ulfc@calypso.engr.sgi.com>
  48 PPC             Geoff Keating <geoffk@redhat.com>
  49 SH              Jörn Rennecke <amylaar@redhat.com>
  50 SH              Hans-Peter Nilsson <hp@bitrange.com>
  51 SPARC           Jakub Jelinek <jakub@redhat.com>
  52 68HC11 68HC12   Stephane Carrez <Stephane.Carrez@worldnet.fr>
  53 DWARF2          Jason Merrill <jason@redhat.com>
  54 x86_64          Jan Hubicka <jh@suse.cz>
  55 x86_64          Andreas Jaeger <aj@suse.de>
  56
  57                --------- CGEN Maintainers -------------
  58
  59 CGEN is a tool for building, amongst other things, assemblers,
  60 disassemblers and simulators from a single description of a CPU.  It
  61 creates files in several of the binutils directories, but it is
  62 mentioned here since there is a single group that maintains CGEN and
  63 the files that it creates.
  64
  65 If you have CGEN related problems you can send email to;
  66
  67              cgen@sources.redhat.com
  68
  69 The current CGEN maintainers are:
  70
  71   Doug Evans, Ben Elliston, Frank Eigler
  72
  73                --------- Write After Approval ---------
  74
  75 Individuals with "write after approval" have the ability to check in
  76 changes, but they must get approval for each change from someone in
  77 one of the above lists (blanket write or maintainers).
  78
  79 [It's a huge list, folks.  You know who you are.  If you have the
  80  *ability* to do binutils checkins, you're in this group.  Just remember
  81  to get approval before checking anything in.]
  82
  83                -------------  Obvious Fixes -------------
  84
  85 Fixes for obvious mistakes do not need approval, and can be checked in
  86 right away, but the patch should still be sent to the binutils list.
  87 The definition of obvious is a bit hazy, and if you are not sure, then
  88 you should seek approval first.  Obvious fixes include fixes for
  89 spelling mistakes, blatantly incorrect code (where the correct code is
  90 also blatantly obvious), and so on.  Obvious fixes should always be
  91 small, the larger they are, the more likely it is that they contain
  92 some un-obvious side effect or consequence.