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    or    binutils@sources.redhat.com
  18
  19 with "[Patch]" as part of the subject line.  Note - patches to the
  20 top level config.guess and config.sub scripts should be sent to:
  21
  22   config-patches@gnu.org
  23
  24 and not to the binutils lists.  Patches to the other top level
  25 configure files (configure, configure.in, config-if, config-ml.in)
  26 should be sent to the binutils lists, and copied to the gcc and gdb
  27 lists as well (gcc-patches@gcc.gnu.org and
  28 gdb-patches@sources.redhat.com).
  29
  30                 --------- Blanket Write Privs ---------
  31
  32 The following people have permission to check patches into the
  33 repository without obtaining approval first:
  34
  35   Nick Clifton <nickc@redhat.com> (head maintainer)
  36   Richard Henderson <rth@redhat.com>
  37   Ian Taylor <ian@wasabisystems.com>
  38   Jeff Law <law@redhat.com>
  39   Jim Wilson <wilson@specifixinc.com>
  40   DJ Delorie <dj@redhat.com>
  41   Alan Modra <amodra@bigpond.net.au>
  42   Michael Meissner <gnu@the-meissners.org>
  43
  44       --------- Maintainers ---------
  45
  46 Maintainers are individuals who are responsible for, and have
  47 permission to check in changes in, certain subsets of the code.  Note
  48 that maintainers still need approval to check in changes outside of
  49 the immediate domain that they maintain.
  50
  51 If there is no maintainer for a given domain then the responsibility
  52 falls to the head maintainer (above).  If there are several
  53 maintainers for a given domain then responsibility falls to the first
  54 maintainer.  The first maintainer is free to devolve that
  55 responsibility among the other maintainers.
  56
  57   ALPHA            Richard Henderson <rth@redhat.com>
  58   ARM              Nick Clifton <nickc@redhat.com>
  59   ARM              Richard Earnshaw <rearnsha@arm.com>
  60   AVR              Denis Chertykov <denisc@overta.ru>
  61   AVR              Marek Michalkiewicz <marekm@amelek.gda.pl>
  62   CONFIGURE        Ben Elliston <bje@wasabisystems.com>
  63   CRIS             Hans-Peter Nilsson <hp@axis.com>
  64   DWARF2           Jason Merrill <jason@redhat.com>
  65   FR30             Dave Brolley <brolley@redhat.com>
  66   FRV              Dave Brolley <brolley@redhat.com>
  67   HPPA             Dave Anglin <dave.anglin@nrc.ca>
  68   HPPA elf32       Alan Modra <amodra@bigpond.net.au>
  69   HPPA elf64       Jeff Law <law@redhat.com> [Basic maintainance only]
  70   IA-64            Jim Wilson <wilson@specifixinc.com>
  71   IQ2000           Stan Cox <scox@redhat.com>
  72   i860             Jason Eckhardt <jle@rice.edu>
  73   ix86             Alan Modra <amodra@bigpond.net.au>
  74   ix86 PE          Christopher Faylor <cgf@redhat.com>
  75   ix86 COFF        DJ Delorie <dj@redhat.com>
  76   ix86             H.J.Lu <hjl@gnu.org>
  77   ix86 INTEL MODE  Diego Novillo <dnovillo@redhat.com>
  78   M68HC11 M68HC12  Stephane Carrez <stcarrez@nerim.fr>
  79   M68k             Ben Elliston <bje@wasabisystems.com>
  80   MIPS             Eric Christopher <echristo@redhat.com>
  81   MIPS             Thiemo Seufer <seufer@csv.ica.uni-stuttgart.de>
  82   MMIX             Hans-Peter Nilsson <hp@bitrange.com>
  83   MN10300          Eric Christopher <echristo@redhat.com>
  84   MN10300          Alexandre Oliva <aoliva@redhat.com>
  85   PPC              Geoff Keating <geoffk@geoffk.org>
  86   PPC vector ext   Aldy Hernandez <aldyh@redhat.com>
  87   s390, s390x      Martin Schwidefsky <schwidefsky@de.ibm.com>
  88   SH               Jörn Rennecke <joern.rennecke@superh.com>
  89   SH               Alexandre Oliva <aoliva@redhat.com>
  90   SH               Kaz Kojima <kkojima@rr.iij4u.or.jp>
  91   SPARC            Jakub Jelinek <jakub@redhat.com>
  92   TESTSUITES       Ben Elliston <bje@wasabisystems.com>
  93   TIC4X            Svein Seldal <svein.seldal@solidas.com>
  94   TIC54X           Timothy Wall <twall@alum.mit.edu>
  95   VAX              Jason R Thorpe <thorpej@wasabisystems.com>
  96   x86_64           Jan Hubicka <jh@suse.cz>
  97   x86_64           Andreas Jaeger <aj@suse.de>
  98   Xtensa           Bob Wilson <bob.wilson@acm.org>
  99   z8k              Christian Groessler <chris@groessler.org>
 100
 101
 102       --------- CGEN Maintainers -------------
 103
 104 CGEN is a tool for building, amongst other things, assemblers,
 105 disassemblers and simulators from a single description of a CPU.
 106 It creates files in several of the binutils directories, but it
 107 is mentioned here since there is a single group that maintains
 108 CGEN and the files that it creates.
 109
 110 If you have CGEN related problems you can send email to;
 111
 112    cgen@sources.redhat.com
 113
 114 The current CGEN maintainers are:
 115
 116   Doug Evans, Ben Elliston, Frank Eigler
 117
 118      --------- Write After Approval ---------
 119
 120 Individuals with "write after approval" have the ability to check in
 121 changes, but they must get approval for each change from someone in
 122 one of the above lists (blanket write or maintainers).
 123
 124 [It's a huge list, folks.  You know who you are.  If you have the
 125  *ability* to do binutils checkins, you're in this group.  Just
 126  remember to get approval before checking anything in.]
 127
 128      -------------  Obvious Fixes -------------
 129
 130 Fixes for obvious mistakes do not need approval, and can be checked in
 131 right away, but the patch should still be sent to the binutils list.
 132 The definition of obvious is a bit hazy, and if you are not sure, then
 133 you should seek approval first.  Obvious fixes include fixes for
 134 spelling mistakes, blatantly incorrect code (where the correct code is
 135 also blatantly obvious), and so on.  Obvious fixes should always be
 136 small, the larger they are, the more likely it is that they contain
 137 some un-obvious side effect or consequence.
 138
 139     --------- Branch Checkins ---------
 140
 141 If a patch is approved for check in to the mainline sources, it can
 142 also be checked into the current release branch.  Normally however
 143 only bug fixes should be applied to the branch.  New features, new
 144 ports, etc, should be restricted to the mainline.  (Otherwise the
 145 burden of maintaining the branch in sync with the mainline becomes too
 146 great).  If you are uncertain as to whether a patch is appropriate for
 147 the branch, ask the branch maintainer.  This is:
 148
 149    Daniel Jacobowitz  <dan@debian.org>
 150
 151     -------- Testsuites ---------------
 152
 153 In general patches to any of the binutils testsuites should be
 154 considered generic and sent to the binutils mailing list for
 155 approval.  Patches to target specific tests are the responsibility the
 156 relevent port maintainer(s), and can be approved/checked in by them.
 157 Other testsuite patches need the approval of a blanket-write-priveleges
 158 person.
 159
 160     -------- Configure patches ----------
 161
 162 Patches to the top level configure files (config.sub & config.guess)
 163 are not the domain of the binutils project and they cannot be approved
 164 by the binutils group.  Instead they should be submitted to the config
 165 maintainer at:
 166
 167         config-patches@gnu.org