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