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