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