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