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.ac, 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 Patches to the libiberty sources should be sent to
  31 gcc-patches@gcc.gnu.org.
  32
  33                 --------- Blanket Write Privs ---------
  34
  35 The following people have permission to check patches into the
  36 repository without obtaining approval first:
  37
  38   Nick Clifton <nickc@redhat.com> (head maintainer)
  39   Ian Lance Taylor <ian@airs.com>
  40   Jeff Law <law@redhat.com>
  41   Jim Wilson <wilson@tuliptree.org>
  42   DJ Delorie <dj@redhat.com>
  43   Alan Modra <amodra@gmail.com>
  44   Michael Meissner <gnu@the-meissners.org>
  45   Daniel Jacobowitz <drow@false.org>
  46   Richard Sandiford <rdsandiford@googlemail.com>
  47
  48       --------- Maintainers ---------
  49
  50 Maintainers are individuals who are responsible for, and have
  51 permission to check in changes in, certain subsets of the code.  Note
  52 that maintainers still need approval to check in changes outside of
  53 the immediate domain that they maintain.
  54
  55 If there is no maintainer for a given domain then the responsibility
  56 falls to the head maintainer (above).  If there are several
  57 maintainers for a given domain then responsibility falls to the first
  58 maintainer.  The first maintainer is free to devolve that
  59 responsibility among the other maintainers.
  60
  61   ALPHA            Richard Henderson <rth@twiddle.net>
  62   AARCH64          Richard Earnshaw <rearnsha@arm.com>
  63   AARCH64          Marcus Shawcroft <marcus.shawcroft@arm.com>
  64   ARC              Claudiu Zissulescu <claziss@synopsys.com>
  65   ARM              Nick Clifton <nickc@redhat.com>
  66   ARM              Richard Earnshaw <rearnsha@arm.com>
  67   ARM              Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
  68   AVR              Denis Chertykov <chertykov@gmail.com>
  69   AVR              Marek Michalkiewicz <marekm@amelek.gda.pl>
  70   BFIN             Jie Zhang <jzhang918@gmail.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   C-SKY            Lifang Xia <lifang_xia@c-sky.com>
  77   C-SKY            Yunhai Shang <yunhai_shang@c-sky.com>
  78   DLX              Nikolaos Kavvadias <nkavv@physics.auth.gr>
  79   DWARF2           Jason Merrill <jason@redhat.com>
  80   DWARF2           Jakub Jelinek <jakub@redhat.com>
  81   dwarf-mode.el    Tom Tromey <tom@tromey.com>
  82   EPIPHANY         Joern Rennecke <joern.rennecke@embecosm.com>
  83   FR30             Dave Brolley <brolley@redhat.com>
  84   FRV              Dave Brolley <brolley@redhat.com>
  85   FRV              Alexandre Oliva <aoliva@redhat.com>
  86   GOLD             Ian Lance Taylor <iant@google.com>
  87   GOLD             Cary Coutant <ccoutant@gmail.com>
  88   H8300            Prafulla Thakare <prafulla.thakare@kpitcummins.com>
  89   HPPA             Dave Anglin <dave.anglin@bell.net>
  90   HPPA elf32       Alan Modra <amodra@gmail.com>
  91   HPPA elf64       Jeff Law <law@redhat.com> [Basic maintainance only]
  92   IA-64            Jim Wilson <wilson@tuliptree.org>
  93   IQ2000           Stan Cox <scox@redhat.com>
  94   ix86             H.J. Lu <hjl.tools@gmail.com>
  95   ix86 PE          Christopher Faylor <me+binutils@cgf.cx>
  96   ix86 COFF        DJ Delorie <dj@redhat.com>
  97   ix86 PE/COFF     Dave Korn <dave.korn.cygwin@gmail.com>
  98   ix86 INTEL MODE  Jan Beulich <jbeulich@novell.com>
  99   LM32             Jon Beniston <jon@beniston.com>
 100   M32R             Doug Evans <dje@sebabeach.org>
 101   M68HC11 M68HC12  Stephane Carrez <Stephane.Carrez@gmail.com>
 102   M68HC11 M68HC12  Sean Keys <skeys@ipdatasys.com>
 103   MACH-O           Tristan Gingold <tgingold@free.fr>
 104   MAXQ             Inderpreet Singh <inderpreetb@noida.hcltech.com>
 105   MEP              Dave Brolley <brolley@redhat.com>
 106   METAG            Markos Chandras <markos.chandras@imgtec.com>
 107   MICROBLAZE       Michael Eager <eager@eagercon.com>
 108   MIPS I-IV        Maciej W. Rozycki <macro@linux-mips.org>
 109   MMIX             Hans-Peter Nilsson <hp@bitrange.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   RISC-V           Palmer Dabbelt <palmer@sifive.com>
 125   RISC-V           Andrew Waterman <andrew@sifive.com>
 126   RISC-V           Jim Wilson <jimw@sifive.com>
 127   RX               Nick Clifton <nickc@redhat.com>
 128   s390, s390x      Martin Schwidefsky <schwidefsky@de.ibm.com>
 129   s390, s390x      Andreas Krebbel <krebbel@linux.vnet.ibm.com>
 130   SH               Alexandre Oliva <aoliva@redhat.com>
 131   SPARC            David S. Miller <davem@davemloft.net>
 132   SPARC            Jose E. Marchesi <jose.marchesi@oracle.com>
 133   SPU              Alan Modra <amodra@gmail.com>
 134   TIC54X           Timothy Wall <twall@alum.mit.edu>
 135   TIC6X            Joseph Myers <joseph@codesourcery.com>
 136   TILE-Gx          Walter Lee <walt@tilera.com>
 137   TILEPro          Walter Lee <walt@tilera.com>
 138   VAX              Matt Thomas <matt@netbsd.org>
 139   VAX              Jan-Benedict Glaw <jbglaw@lug-owl.de>
 140   Visium           Eric Botcazou <ebotcazou@libertysurf.fr>
 141   VMS              Tristan Gingold <tgingold@free.fr>
 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   z8k              Christian Groessler <chris@groessler.org>
 149
 150       --------- Past Maintainers -------------
 151
 152 These folks have acted as maintainers in the past, but have now
 153 moved on to other things.  Our thanks for all their hard work
 154 goes with them.
 155
 156   Paul Brook
 157   Eric Christopher
 158   Jason Eckhardt
 159   Mark Kettenis
 160   Mei Ligang
 161   Arnold Metselaar
 162   Mark Mitchell
 163   Bernd Schmidt
 164   Svein Seldal
 165
 166       --------- CGEN Maintainers -------------
 167
 168 CGEN is a tool for building, amongst other things, assemblers,
 169 disassemblers and simulators from a single description of a CPU.
 170 It creates files in several of the binutils directories, but it
 171 is mentioned here since there is a single group that maintains
 172 CGEN and the files that it creates.
 173
 174 If you have CGEN related problems you can send email to;
 175
 176    cgen@sourceware.org
 177
 178 The current CGEN maintainers are:
 179
 180   Doug Evans, Frank Eigler
 181
 182      --------- Write After Approval ---------
 183
 184 Individuals with "write after approval" have the ability to check in
 185 changes, but they must get approval for each change from someone in
 186 one of the above lists (blanket write or maintainers).
 187
 188 [It's a huge list, folks.  You know who you are.  If you have the
 189  *ability* to do binutils checkins, you're in this group.  Just
 190  remember to get approval before checking anything in.]
 191
 192      -------------  Obvious Fixes -------------
 193
 194 Fixes for obvious mistakes do not need approval, and can be checked in
 195 right away, but the patch should still be sent to the binutils list.
 196 The definition of obvious is a bit hazy, and if you are not sure, then
 197 you should seek approval first.  Obvious fixes include fixes for
 198 spelling mistakes, blatantly incorrect code (where the correct code is
 199 also blatantly obvious), and so on.  Obvious fixes should always be
 200 small, the larger they are, the more likely it is that they contain
 201 some un-obvious side effect or consequence.
 202
 203     --------- Branch Checkins ---------
 204
 205 If a patch is approved for check in to the mainline sources, it can
 206 also be checked into the current release branch.  Normally however
 207 only bug fixes should be applied to the branch.  New features, new
 208 ports, etc, should be restricted to the mainline.  (Otherwise the
 209 burden of maintaining the branch in sync with the mainline becomes too
 210 great).  If you are uncertain as to whether a patch is appropriate for
 211 the branch, ask the branch maintainer.  This is:
 212
 213    (cf global maintainers)
 214
 215     -------- Testsuites ---------------
 216
 217 In general patches to any of the binutils testsuites should be
 218 considered generic and sent to the binutils mailing list for
 219 approval.  Patches to target specific tests are the responsibility the
 220 relevant port maintainer(s), and can be approved/checked in by them.
 221 Other testsuite patches need the approval of a blanket-write-priveleges
 222 person.
 223
 224     -------- Configure patches ----------
 225
 226 Patches to the top level configure files (config.sub & config.guess)
 227 are not the domain of the binutils project and they cannot be approved
 228 by the binutils group.  Instead they should be submitted to the config
 229 maintainer at:
 230
 231         config-patches@gnu.org
 232
 233     --------- Creating Branches ---------
 234
 235 Anyone with at least write-after-approval access may create a branch
 236 to use for their own development purposes.  In keeping with FSF
 237 policies, all patches applied to such a branch must come from people
 238 with appropriate copyright assignments on file.  All legal
 239 requirements that would apply to any other contribution apply equally
 240 to contributions on a branch.
 241
 242 Before creating the branch, you should select a name for the branch of
 243 the form:
 244
 245   binutils-<org>-<name>
 246
 247 where "org" is the initials of your organization, or your own initials
 248 if you are acting as an individual.  For example, for a branch created
 249 by The GNUDist Company, "tgc" would be an appropriate choice for
 250 "org".  It's up to each organization to select an appropriate choice
 251 for "name"; some organizations may use more structure than others, so
 252 "name" may contain additional hyphens.
 253
 254 Suppose that The GNUDist Company was creating a branch to develop a
 255 port of Binutils to the FullMonty processor.  Then, an appropriate
 256 choice of branch name would be:
 257
 258   binutils-tgc-fm
 259
 260 A date stamp is not required as part of the name field, but some
 261 organizations like to have one.  If you do include the date, you
 262 should follow these rules:
 263
 264 1. The date should be the date that the branch was created.
 265
 266 2. The date should be numerical and in the form YYYYMMDD.
 267
 268 For example:
 269
 270   binutils-tgc-fm_20050101
 271
 272 would be appropriate if the branch was created on January 1st, 2005.
 273
 274 Having selected the branch name, create the branch as follows:
 275
 276 1. Check out binutils, so that you have a git checkout corresponding
 277    to the initial state of your branch.
 278
 279 2. Create a tag:
 280
 281      git tag binutils-<org>-<name>-branchpoint
 282
 283    That tag will allow you, and others, to easily determine what's
 284    changed on the branch relative to the initial state.
 285
 286 3. Create and push the branch:
 287
 288      git checkout -b binutils-<org>-<name>-branch
 289      git push origin HEAD
 290
 291 4. Document the branch:
 292
 293      Add a description of the branch to binutils/BRANCHES, and check
 294      that file in.  All branch descriptions should be added to the
 295      HEAD revision of the file; it doesn't help to modify
 296      binutils/BRANCHES on a branch!
 297
 298 Please do not commit any patches to a branch you did not create
 299 without the explicit permission of the person who created the branch.
 300 \f
 301 Copyright (C) 2012-2018 Free Software Foundation, Inc.
 302
 303 Copying and distribution of this file, with or without modification,
 304 are permitted in any medium without royalty provided the copyright
 305 notice and this notice are preserved.