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