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   binutils@sourceware.org
  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@sourceware.org).
  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@tuliptree.org>
  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   Richard Sandiford <rdsandiford@googlemail.com>
  45
  46       --------- Maintainers ---------
  47
  48 Maintainers are individuals who are responsible for, and have
  49 permission to check in changes in, certain subsets of the code.  Note
  50 that maintainers still need approval to check in changes outside of
  51 the immediate domain that they maintain.
  52
  53 If there is no maintainer for a given domain then the responsibility
  54 falls to the head maintainer (above).  If there are several
  55 maintainers for a given domain then responsibility falls to the first
  56 maintainer.  The first maintainer is free to devolve that
  57 responsibility among the other maintainers.
  58
  59   ALPHA            Richard Henderson <rth@redhat.com>
  60   ARM              Nick Clifton <nickc@redhat.com>
  61   ARM              Richard Earnshaw <rearnsha@arm.com>
  62   ARM              Paul Brook <paul@codesourcery.com>
  63   ARM (Symbian)    Mark Mitchell <mark@codesourcery.com>
  64   AVR              Denis Chertykov <denisc@overta.ru>
  65   AVR              Marek Michalkiewicz <marekm@amelek.gda.pl>
  66   BFIN             Jie Zhang <jie.zhang@analog.com>
  67   BFIN             Bernd Schmidt <bernd.schmidt@analog.com>
  68   BUILD SYSTEM     Daniel Jacobowitz <dan@debian.org>
  69   CR16             M R Swami Reddy <MR.Swami.Reddy@nsc.com>
  70   CRIS             Hans-Peter Nilsson <hp@axis.com>
  71   CRX              M R Swami Reddy <MR.Swami.Reddy@nsc.com>
  72   DLX              Nikolaos Kavvadias <nkavv@physics.auth.gr>
  73   DWARF2           Jason Merrill <jason@redhat.com>
  74   FR30             Dave Brolley <brolley@redhat.com>
  75   FRV              Dave Brolley <brolley@redhat.com>
  76   FRV              Alexandre Oliva <aoliva@redhat.com>
  77   H8300            Prafulla Thakare <prafulla.thakare@kpitcummins.com>
  78   HPPA             Dave Anglin <dave.anglin@nrc.ca>
  79   HPPA elf32       Alan Modra <amodra@bigpond.net.au>
  80   HPPA elf64       Jeff Law <law@redhat.com> [Basic maintainance only]
  81   IA-64            Jim Wilson <wilson@tuliptree.org>
  82   IQ2000           Stan Cox <scox@redhat.com>
  83   i860             Jason Eckhardt <jle@rice.edu>
  84   ix86             H.J. Lu <hjl.tools@gmail.com>
  85   ix86 PE          Christopher Faylor <me+binutils@cgf.cx>
  86   ix86 COFF        DJ Delorie <dj@redhat.com>
  87   ix86 PE/COFF     Dave Korn <dave.korn.cygwin@gmail.com>
  88   ix86 INTEL MODE  Jan Beulich <jbeulich@novell.com>
  89   LM32             Jon Beniston <jon@beniston.com>
  90   M32R             Doug Evans <dje@sebabeach.org>
  91   M68HC11 M68HC12  Stephane Carrez <stcarrez@nerim.fr>
  92   M88k             Mark Kettenis <kettenis@gnu.org>
  93   MACH-O           Tristan Gingold <gingold@adacore.com>
  94   MAXQ             Inderpreet Singh <inderpreetb@noida.hcltech.com>
  95   MEP              Dave Brolley <brolley@redhat.com>
  96   MICROBLAZE       Michael Eager <eager@eagercon.com>
  97   MIPS             Eric Christopher <echristo@apple.com>
  98   MMIX             Hans-Peter Nilsson <hp@bitrange.com>
  99   MN10300          Eric Christopher <echristo@apple.com>
 100   MN10300          Alexandre Oliva <aoliva@redhat.com>
 101   Moxie            Anthony Green <green@moxielogic.com>
 102   MSP430           Dmitry Diky <diwil@spec.ru>
 103   NetBSD support   Matt Thomas <matt@netbsd.org>
 104   PPC              Geoff Keating <geoffk@geoffk.org>
 105   PPC              Alan Modra <amodra@bigpond.net.au>
 106   PPC vector ext   Aldy Hernandez <aldyh@redhat.com>
 107   RX               DJ Delorie <dj@redhat.com>
 108   RX               Nick Clifton <nickc@redhat.com>
 109   s390, s390x      Martin Schwidefsky <schwidefsky@de.ibm.com>
 110   SCORE            Mei Ligang <ligang@sunnorth.com.cn>
 111   SH               Alexandre Oliva <aoliva@redhat.com>
 112   SH               Kaz Kojima <kkojima@rr.iij4u.or.jp>
 113   SPARC            Jakub Jelinek <jakub@redhat.com>
 114   SPU              Alan Modra <amodra@bigpond.net.au>
 115   TIC4X            Svein Seldal <svein@dev.seldal.com>
 116   TIC54X           Timothy Wall <twall@alum.mit.edu>
 117   VAX              Matt Thomas <matt@netbsd.org>
 118   VAX              Jan-Benedict Glaw <jbglaw@lug-owl.de>
 119   VMS              Tristan Gingold <gingold@adacore.com>
 120   x86_64           Jan Hubicka <jh@suse.cz>
 121   x86_64           Andreas Jaeger <aj@suse.de>
 122   x86_64           H.J. Lu <hjl.tools@gmail.com>
 123   XCOFF            Richard Sandiford <r.sandiford@uk.ibm.com>
 124   Xtensa           Sterling Augustine <sterling@tensilica.com>
 125   z80              Arnold Metselaar <arnold.metselaar@planet.nl>
 126   z8k              Christian Groessler <chris@groessler.org>
 127
 128
 129       --------- CGEN Maintainers -------------
 130
 131 CGEN is a tool for building, amongst other things, assemblers,
 132 disassemblers and simulators from a single description of a CPU.
 133 It creates files in several of the binutils directories, but it
 134 is mentioned here since there is a single group that maintains
 135 CGEN and the files that it creates.
 136
 137 If you have CGEN related problems you can send email to;
 138
 139    cgen@sourceware.org
 140
 141 The current CGEN maintainers are:
 142
 143   Doug Evans, Frank Eigler
 144
 145      --------- Write After Approval ---------
 146
 147 Individuals with "write after approval" have the ability to check in
 148 changes, but they must get approval for each change from someone in
 149 one of the above lists (blanket write or maintainers).
 150
 151 [It's a huge list, folks.  You know who you are.  If you have the
 152  *ability* to do binutils checkins, you're in this group.  Just
 153  remember to get approval before checking anything in.]
 154
 155      -------------  Obvious Fixes -------------
 156
 157 Fixes for obvious mistakes do not need approval, and can be checked in
 158 right away, but the patch should still be sent to the binutils list.
 159 The definition of obvious is a bit hazy, and if you are not sure, then
 160 you should seek approval first.  Obvious fixes include fixes for
 161 spelling mistakes, blatantly incorrect code (where the correct code is
 162 also blatantly obvious), and so on.  Obvious fixes should always be
 163 small, the larger they are, the more likely it is that they contain
 164 some un-obvious side effect or consequence.
 165
 166     --------- Branch Checkins ---------
 167
 168 If a patch is approved for check in to the mainline sources, it can
 169 also be checked into the current release branch.  Normally however
 170 only bug fixes should be applied to the branch.  New features, new
 171 ports, etc, should be restricted to the mainline.  (Otherwise the
 172 burden of maintaining the branch in sync with the mainline becomes too
 173 great).  If you are uncertain as to whether a patch is appropriate for
 174 the branch, ask the branch maintainer.  This is:
 175
 176    Daniel Jacobowitz  <dan@debian.org>
 177
 178     -------- Testsuites ---------------
 179
 180 In general patches to any of the binutils testsuites should be
 181 considered generic and sent to the binutils mailing list for
 182 approval.  Patches to target specific tests are the responsibility the
 183 relevent port maintainer(s), and can be approved/checked in by them.
 184 Other testsuite patches need the approval of a blanket-write-priveleges
 185 person.
 186
 187     -------- Configure patches ----------
 188
 189 Patches to the top level configure files (config.sub & config.guess)
 190 are not the domain of the binutils project and they cannot be approved
 191 by the binutils group.  Instead they should be submitted to the config
 192 maintainer at:
 193
 194         config-patches@gnu.org
 195
 196     --------- Creating Branches ---------
 197
 198 Anyone with at least write-after-approval access may create a branch
 199 to use for their own development purposes.  In keeping with FSF
 200 policies, all patches applied to such a branch must come from people
 201 with appropriate copyright assignments on file.  All legal
 202 requirements that would apply to any other contribution apply equally
 203 to contributions on a branch.
 204
 205 Before creating the branch, you should select a name for the branch of
 206 the form:
 207
 208   binutils-<org>-<name>
 209
 210 where "org" is the initials of your organization, or your own initials
 211 if you are acting as an individual.  For example, for a branch created
 212 by The GNUDist Company, "tgc" would be an appropriate choice for
 213 "org".  It's up to each organization to select an appropriate choice
 214 for "name"; some organizations may use more structure than others, so
 215 "name" may contain additional hyphens.
 216
 217 Suppose that The GNUDist Company was creating a branch to develop a
 218 port of Binutils to the FullMonty processor.  Then, an appropriate
 219 choice of branch name would be:
 220
 221   binutils-tgc-fm
 222
 223 A date stamp is not required as part of the name field, but some
 224 organizations like to have one.  If you do include the date, you
 225 should follow these rules:
 226
 227 1. The date should be the date that the branch was created.
 228
 229 2. The date should be numerical and in the form YYYYMMDD.
 230
 231 For example:
 232
 233   binutils-tgc-fm_20050101
 234
 235 would be appropriate if the branch was created on January 1st, 2005.
 236
 237 Having selected the branch name, create the branch as follows:
 238
 239 1. Check out binutils, so that you have a CVS checkout corresponding
 240    to the initial state of your branch.
 241
 242 2. Create a tag:
 243
 244      cvs tag binutils-<org>-<name>-branchpoint
 245
 246    That tag will allow you, and others, to easily determine what's
 247    changed on the branch relative to the initial state.
 248
 249 3. Create the branch:
 250
 251      cvs rtag -b -r binutils-<org>-<name>-branchpoint \
 252        binutils-<org>-<name>-branch
 253
 254 4. Document the branch:
 255
 256      Add a description of the branch to binutils/BRANCHES, and check
 257      that file in.  All branch descriptions should be added to the
 258      HEAD revision of the file; it doesn't help to modify
 259      binutils/BRANCHES on a branch!
 260
 261 Please do not commit any patches to a branch you did not create
 262 without the explicit permission of the person who created the branch.