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-ml.in) should
  26 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 Lance Taylor <ian@airs.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   Daniel Jacobowitz <dan@debian.org>
  44
  45       --------- Maintainers ---------
  46
  47 Maintainers are individuals who are responsible for, and have
  48 permission to check in changes in, certain subsets of the code.  Note
  49 that maintainers still need approval to check in changes outside of
  50 the immediate domain that they maintain.
  51
  52 If there is no maintainer for a given domain then the responsibility
  53 falls to the head maintainer (above).  If there are several
  54 maintainers for a given domain then responsibility falls to the first
  55 maintainer.  The first maintainer is free to devolve that
  56 responsibility among the other maintainers.
  57
  58   ALPHA            Richard Henderson <rth@redhat.com>
  59   ARM              Nick Clifton <nickc@redhat.com>
  60   ARM              Richard Earnshaw <rearnsha@arm.com>
  61   ARM (Symbian)    Paul Brook <paul@codesourcery.com>
  62   ARM (Symbian)    Mark Mitchell <mark@codesourcery.com>
  63   AVR              Denis Chertykov <denisc@overta.ru>
  64   AVR              Marek Michalkiewicz <marekm@amelek.gda.pl>
  65   BUILD SYSTEM     Ben Elliston <bje@gnu.org>
  66   BUILD SYSTEM     Daniel Jacobowitz <dan@debian.org>
  67   CRIS             Hans-Peter Nilsson <hp@axis.com>
  68   CRX              Tomer Levi <Tomer.Levi@nsc.com>
  69   DWARF2           Jason Merrill <jason@redhat.com>
  70   FR30             Dave Brolley <brolley@redhat.com>
  71   FRV              Dave Brolley <brolley@redhat.com>
  72   FRV              Alexandre Oliva <aoliva@redhat.com>
  73   H8300            Anil Paranjpe <anilp1@kpitcummins.com>
  74   HPPA             Dave Anglin <dave.anglin@nrc.ca>
  75   HPPA elf32       Alan Modra <amodra@bigpond.net.au>
  76   HPPA elf64       Jeff Law <law@redhat.com> [Basic maintainance only]
  77   IA-64            Jim Wilson <wilson@specifixinc.com>
  78   IQ2000           Stan Cox <scox@redhat.com>
  79   i860             Jason Eckhardt <jle@rice.edu>
  80   ix86             Alan Modra <amodra@bigpond.net.au>
  81   ix86 PE          Christopher Faylor <cgf@redhat.com>
  82   ix86 COFF        DJ Delorie <dj@redhat.com>
  83   ix86             H.J.Lu <hjl@gnu.org>
  84   M68HC11 M68HC12  Stephane Carrez <stcarrez@nerim.fr>
  85   M68k             Ben Elliston <bje@gnu.org>
  86   M88k             Mark Kettenis <kettenis@gnu.org>
  87   MAXQ             Inderpreet Singh <inderpreetb@noida.hcltech.com>
  88   MIPS             Eric Christopher <echristo@redhat.com>
  89   MIPS             Thiemo Seufer <ths@networkno.de>
  90   MMIX             Hans-Peter Nilsson <hp@bitrange.com>
  91   MN10300          Eric Christopher <echristo@redhat.com>
  92   MN10300          Alexandre Oliva <aoliva@redhat.com>
  93   MSP430           Dmitry Diky <diwil@spec.ru>
  94   PPC              Geoff Keating <geoffk@geoffk.org>
  95   PPC vector ext   Aldy Hernandez <aldyh@redhat.com>
  96   s390, s390x      Martin Schwidefsky <schwidefsky@de.ibm.com>
  97   SH               Jörn Rennecke <joern.rennecke@superh.com>
  98   SH               Alexandre Oliva <aoliva@redhat.com>
  99   SH               Kaz Kojima <kkojima@rr.iij4u.or.jp>
 100   SPARC            Jakub Jelinek <jakub@redhat.com>
 101   TESTSUITES       Ben Elliston <bje@gnu.org>
 102   TIC4X            Svein Seldal <svein@dev.seldal.com>
 103   TIC54X           Timothy Wall <twall@alum.mit.edu>
 104   VAX              Jason R Thorpe <thorpej@netbsd.org>
 105   x86_64           Jan Hubicka <jh@suse.cz>
 106   x86_64           Andreas Jaeger <aj@suse.de>
 107   Xtensa           Bob Wilson <bob.wilson@acm.org>
 108   z8k              Christian Groessler <chris@groessler.org>
 109
 110
 111       --------- CGEN Maintainers -------------
 112
 113 CGEN is a tool for building, amongst other things, assemblers,
 114 disassemblers and simulators from a single description of a CPU.
 115 It creates files in several of the binutils directories, but it
 116 is mentioned here since there is a single group that maintains
 117 CGEN and the files that it creates.
 118
 119 If you have CGEN related problems you can send email to;
 120
 121    cgen@sources.redhat.com
 122
 123 The current CGEN maintainers are:
 124
 125   Doug Evans, Ben Elliston, Frank Eigler
 126
 127      --------- Write After Approval ---------
 128
 129 Individuals with "write after approval" have the ability to check in
 130 changes, but they must get approval for each change from someone in
 131 one of the above lists (blanket write or maintainers).
 132
 133 [It's a huge list, folks.  You know who you are.  If you have the
 134  *ability* to do binutils checkins, you're in this group.  Just
 135  remember to get approval before checking anything in.]
 136
 137      -------------  Obvious Fixes -------------
 138
 139 Fixes for obvious mistakes do not need approval, and can be checked in
 140 right away, but the patch should still be sent to the binutils list.
 141 The definition of obvious is a bit hazy, and if you are not sure, then
 142 you should seek approval first.  Obvious fixes include fixes for
 143 spelling mistakes, blatantly incorrect code (where the correct code is
 144 also blatantly obvious), and so on.  Obvious fixes should always be
 145 small, the larger they are, the more likely it is that they contain
 146 some un-obvious side effect or consequence.
 147
 148     --------- Branch Checkins ---------
 149
 150 If a patch is approved for check in to the mainline sources, it can
 151 also be checked into the current release branch.  Normally however
 152 only bug fixes should be applied to the branch.  New features, new
 153 ports, etc, should be restricted to the mainline.  (Otherwise the
 154 burden of maintaining the branch in sync with the mainline becomes too
 155 great).  If you are uncertain as to whether a patch is appropriate for
 156 the branch, ask the branch maintainer.  This is:
 157
 158    Daniel Jacobowitz  <dan@debian.org>
 159
 160     -------- Testsuites ---------------
 161
 162 In general patches to any of the binutils testsuites should be
 163 considered generic and sent to the binutils mailing list for
 164 approval.  Patches to target specific tests are the responsibility the
 165 relevent port maintainer(s), and can be approved/checked in by them.
 166 Other testsuite patches need the approval of a blanket-write-priveleges
 167 person.
 168
 169     -------- Configure patches ----------
 170
 171 Patches to the top level configure files (config.sub & config.guess)
 172 are not the domain of the binutils project and they cannot be approved
 173 by the binutils group.  Instead they should be submitted to the config
 174 maintainer at:
 175
 176         config-patches@gnu.org
 177
 178     --------- Creating Branches ---------
 179
 180 Anyone with at least write-after-approval access may create a branch
 181 to use for their own development purposes.  In keeping with FSF
 182 policies, all patches applied to such a branch must come from people
 183 with appropriate copyright assignments on file.  All legal
 184 requirements that would apply to any other contribution apply equally
 185 to contributions on a branch.
 186
 187 Before creating the branch, you should select a name for the branch of
 188 the form:
 189
 190   binutils-<org>-<name>
 191
 192 where "org" is the initials of your organization, or your own initials
 193 if you are acting as an individual.  For example, for a branch created
 194 by The GNUDist Company, "tgc" would be an appropriate choice for
 195 "org".  It's up to each organization to select an appropriate choice
 196 for "name"; some organizations may use more structure than others, so
 197 "name" may contain additional hyphens.
 198
 199 Suppose that The GNUDist Company was creating a branch to develop a
 200 port of Binutils to the FullMonty processor.  Then, an appropriate
 201 choice of branch name would be:
 202
 203   binutils-tgc-fm
 204
 205 A data stamp is not required as part of the name field, but some
 206 organizations like to have one.  If you do include the date, you
 207 should follow these rules:
 208
 209 1. The date should be the date that the branch was created.
 210
 211 2. The date should be numerical and in the form YYYYMMDD.
 212
 213 For example:
 214
 215   binutils-tgc-fm_20050101
 216
 217 would be appropriate if the branch was created on January 1st, 2005.
 218
 219 Having selected the branch name, create the branch as follows:
 220
 221 1. Check out binutils, so that you have a CVS checkout corresponding
 222    to the initial state of your branch.
 223
 224 2. Create a tag:
 225
 226      cvs tag binutils-<org>-<name>-branchpoint
 227
 228    That tag will allow you, and others, to easily determine what's
 229    changed on the branch relative to the initial state.
 230
 231 3. Create the branch:
 232
 233      cvs rtag -b -r binutils-<org>-<name>-branchpoint \
 234        binutils-<org>-<name>-branch
 235
 236 4. Document the branch:
 237
 238      Add a description of the branch to binutils/BRANCHES, and check
 239      that file in.  All branch descriptions should be added to the
 240      HEAD revision of the file; it doesn't help to modify
 241      binutils/BRANCHES on a branch!
 242
 243 Please do not commit any patches to a branch you did not create
 244 without the explicit permission of the person who created the branch.