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