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