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