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