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