binutils/MAINTAINERS

   1                 ========= Binutils Maintainers =========
   2
   3 This is the list of individuals responsible for maintenance and update
   4 of the GNU Binary Utilities project.  This includes the linker (ld),
   5 the assembler (gas), the profiler (gprof), a whole suite of other
   6 programs (binutils) and the libraries that they use (bfd and
   7 opcodes).  This project shares a common set of header files with the
   8 GCC and GDB projects (include), so maintainership of those files is
   9 shared amoungst the projects.
  10
  11 The home page for binutils is:
  12
  13   http://www.gnu.org/software/binutils/binutils.html
  14
  15 and patches should be sent to:
  16
  17   bug-binutils@gnu.org
  18
  19 with "[Patch]" as part of the subject line.  Note - patches to the
  20 top level configure.in and config.sub scripts should be sent to:
  21
  22   config-patches@gnu.org
  23
  24 and not to the binutils list.
  25
  26                 --------- Blanket Write Privs ---------
  27
  28 The following people have permission to check patches into the
  29 repository without obtaining approval first:
  30
  31   Nick Clifton <nickc@redhat.com> (head maintainer)
  32   Richard Henderson <rth@redhat.com>
  33   Ian Taylor <ian@zembu.com>
  34   Jeff Law <law@redhat.com>
  35   Jim Wilson <wilson@redhat.com>
  36   DJ Delorie <dj@redhat.com>
  37   Alan Modra <amodra@bigpond.net.au>
  38   Michael Meissner <meissner@redhat.com>
  39
  40       --------- Maintainers ---------
  41
  42 Maintainers are individuals who are responsible for, and have
  43 permission to check in changes in, certain subsets of the code.  Note
  44 that maintainers still need approval to check in changes outside of
  45 the immediate domain that they maintain.
  46
  47 If there is no maintainer for a given domain then the responsibility
  48 falls to the head maintainer (above).  If there are several
  49 maintainers for a given domain then responsibility falls to the first
  50 maintainer.  The first maintainer is free to devolve that
  51 responsibility among the other maintainers.
  52
  53   ARC              Peter Targett <peter.targett@arccores.com>
  54   ARM              Nick Clifton <nickc@redhat.com>
  55   AVR              Denis Chertykov <denisc@overta.ru>
  56   CRIS             Hans-Peter Nilsson <hp@axis.com>
  57   DWARF2           Jason Merrill <jason@redhat.com>
  58   HPPA elf32       Alan Modra <amodra@bigpond.net.au>
  59   IA64             Jim Wilson <wilson@redhat.com>
  60   x86_64           Jan Hubicka <jh@suse.cz>
  61   x86_64           Andreas Jaeger <aj@suse.de>
  62   i860             Jason Eckhardt <jle@redhat.com>
  63   ix86             Alan Modra <amodra@bigpond.net.au>
  64   ix86 COFF,PE     DJ Delorie <dj@redhat.com>
  65   ix86             H.J.Lu <hjl@gnu.org>
  66   ix86 INTEL MODE  Diego Novillo <dnovillo@redhat.com>
  67   M68HC11 M68HC12  Stephane Carrez <Stephane.Carrez@worldnet.fr>
  68   MN10300          Eric Christopher <echristo@redhat.com>
  69   MIPS             Eric Christopher <echristo@redhat.com>
  70   M88k             Ben Elliston <bje@redhat.com>
  71   PPC              Geoff Keating <geoffk@redhat.com>
  72   SH               Jörn Rennecke <amylaar@onetel.net.uk>
  73   SH               Hans-Peter Nilsson <hp@bitrange.com>
  74   SPARC            Jakub Jelinek <jakub@redhat.com>
  75   z8k              Christian Groessler <cpg@aladdin.de>
  76
  77       --------- CGEN Maintainers -------------
  78
  79 CGEN is a tool for building, amongst other things, assemblers,
  80 disassemblers and simulators from a single description of a CPU.
  81 It creates files in several of the binutils directories, but it
  82 is mentioned here since there is a single group that maintains
  83 CGEN and the files that it creates.
  84
  85 If you have CGEN related problems you can send email to;
  86
  87    cgen@sources.redhat.com
  88
  89 The current CGEN maintainers are:
  90
  91   Doug Evans, Ben Elliston, Frank Eigler
  92
  93      --------- Write After Approval ---------
  94
  95 Individuals with "write after approval" have the ability to check in
  96 changes, but they must get approval for each change from someone in
  97 one of the above lists (blanket write or maintainers).
  98
  99 [It's a huge list, folks.  You know who you are.  If you have the
 100  *ability* to do binutils checkins, you're in this group.  Just
 101  remember to get approval before checking anything in.]
 102
 103      -------------  Obvious Fixes -------------
 104
 105 Fixes for obvious mistakes do not need approval, and can be checked in
 106 right away, but the patch should still be sent to the binutils list.
 107 The definition of obvious is a bit hazy, and if you are not sure, then
 108 you should seek approval first.  Obvious fixes include fixes for
 109 spelling mistakes, blatantly incorrect code (where the correct code is
 110 also blatantly obvious), and so on.  Obvious fixes should always be
 111 small, the larger they are, the more likely it is that they contain
 112 some un-obvious side effect or consequence.
 113
 114     --------- Branch Checkins ---------
 115
 116 If a patch is approved for check in to the mainline sources, it can
 117 also be checked into the current release branch.  Normally however
 118 only bug fixes should be applied to the branch.  New features, new
 119 ports, etc, should be restricted to the mainline.  (Otherwise the
 120 burden of maintaining the branch in sync with the mainline becomes too
 121 great).  If you are uncertain as to whether a patch is appropriate for
 122 the branch, ask the branch maintainer.  This is:
 123
 124    Philip Blundell  <philb@gnu.org>