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