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