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