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