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