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