1 ========= Binutils Maintainers =========
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.
11 The home page for binutils is:
13 http://www.gnu.org/software/binutils/binutils.html
15 and patches should be sent to:
17 binutils@sourceware.org
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:
22 config-patches@gnu.org
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).
30 Patches to the libiberty sources should be sent to
31 gcc-patches@gcc.gnu.org.
33 --------- Blanket Write Privs ---------
35 The following people have permission to check patches into the
36 repository without obtaining approval first:
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>
48 --------- Maintainers ---------
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.
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.
61 ALPHA Richard Henderson <rth@twiddle.net>
62 AARCH64 Richard Earnshaw <rearnsha@arm.com>
63 AARCH64 Marcus Shawcroft <marcus.shawcroft@arm.com>
64 ARM Nick Clifton <nickc@redhat.com>
65 ARM Richard Earnshaw <rearnsha@arm.com>
66 ARM Ramana Radhakrishnan <ramana.radhakrishnan@arm.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 Mike Frysinger <vapier@gentoo.org>
71 BUILD SYSTEM Daniel Jacobowitz <drow@false.org>
72 CR16 M R Swami Reddy <MR.Swami.Reddy@nsc.com>
73 CRIS Hans-Peter Nilsson <hp@axis.com>
74 CRX M R Swami Reddy <MR.Swami.Reddy@nsc.com>
75 DLX Nikolaos Kavvadias <nkavv@physics.auth.gr>
76 DWARF2 Jason Merrill <jason@redhat.com>
77 DWARF2 Jakub Jelinek <jakub@redhat.com>
78 dwarf-mode.el Tom Tromey <tom@tromey.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@gmail.com>
85 H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com>
86 HPPA Dave Anglin <dave.anglin@bell.net>
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 ix86 H.J. Lu <hjl.tools@gmail.com>
92 ix86 PE Christopher Faylor <me+binutils@cgf.cx>
93 ix86 COFF DJ Delorie <dj@redhat.com>
94 ix86 PE/COFF Dave Korn <dave.korn.cygwin@gmail.com>
95 ix86 INTEL MODE Jan Beulich <jbeulich@novell.com>
96 LM32 Jon Beniston <jon@beniston.com>
97 M32R Doug Evans <dje@sebabeach.org>
98 M68HC11 M68HC12 Stephane Carrez <Stephane.Carrez@gmail.com>
99 M68HC11 M68HC12 Sean Keys <skeys@ipdatasys.com>
100 MACH-O Tristan Gingold <tgingold@free.fr>
101 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com>
102 MEP Dave Brolley <brolley@redhat.com>
103 METAG Markos Chandras <markos.chandras@imgtec.com>
104 MICROBLAZE Michael Eager <eager@eagercon.com>
105 MIPS I-IV Maciej W. Rozycki <macro@linux-mips.org>
106 MMIX Hans-Peter Nilsson <hp@bitrange.com>
107 MN10300 Alexandre Oliva <aoliva@redhat.com>
108 Moxie Anthony Green <green@moxielogic.com>
109 MSP430 Dmitry Diky <diwil@spec.ru>
110 NDS32 Kuan-Lin Chen <kuanlinchentw@gmail.com>
111 NDS32 Wei-Cheng Wang <cole945@gmail.com>
112 NetBSD support Matt Thomas <matt@netbsd.org>
113 Nios II Sandra Loosemore <sandra@codesourcery.com>
114 Nios II Andrew Jenner <andrew@codesourcery.com>
115 OR1K Christian Svensson <blue@cmd.nu>
116 OR1K Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
117 PPC Geoff Keating <geoffk@geoffk.org>
118 PPC Alan Modra <amodra@gmail.com>
119 PPC Peter Bergner <bergner@vnet.ibm.com>
120 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
121 RISC-V Palmer Dabbelt <palmer@sifive.com>
122 RISC-V Andrew Waterman <andrew@sifive.com>
123 RISC-V Jim Wilson <jimw@sifive.com>
124 RX Nick Clifton <nickc@redhat.com>
125 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
126 s390, s390x Andreas Krebbel <krebbel@linux.vnet.ibm.com>
127 SH Alexandre Oliva <aoliva@redhat.com>
128 SPARC David S. Miller <davem@davemloft.net>
129 SPARC Jose E. Marchesi <jose.marchesi@oracle.com>
130 SPU Alan Modra <amodra@gmail.com>
131 TIC54X Timothy Wall <twall@alum.mit.edu>
132 TIC6X Joseph Myers <joseph@codesourcery.com>
133 TILE-Gx Walter Lee <walt@tilera.com>
134 TILEPro Walter Lee <walt@tilera.com>
135 VAX Matt Thomas <matt@netbsd.org>
136 VAX Jan-Benedict Glaw <jbglaw@lug-owl.de>
137 Visium Eric Botcazou <ebotcazou@libertysurf.fr>
138 VMS Tristan Gingold <tgingold@free.fr>
139 x86_64 Jan Hubicka <jh@suse.cz>
140 x86_64 Andreas Jaeger <aj@suse.de>
141 x86_64 H.J. Lu <hjl.tools@gmail.com>
142 XCOFF Richard Sandiford <r.sandiford@uk.ibm.com>
143 XGATE Sean Keys <skeys@ipdatasys.com>
144 Xtensa Sterling Augustine <augustine.sterling@gmail.com>
145 z80 Arnold Metselaar <arnold.metselaar@planet.nl>
146 z8k Christian Groessler <chris@groessler.org>
148 --------- Past Maintainers -------------
150 These folks have acted as maintainers in the past, but have now
151 moved on to other things. Our thanks for all their hard work
163 --------- CGEN Maintainers -------------
165 CGEN is a tool for building, amongst other things, assemblers,
166 disassemblers and simulators from a single description of a CPU.
167 It creates files in several of the binutils directories, but it
168 is mentioned here since there is a single group that maintains
169 CGEN and the files that it creates.
171 If you have CGEN related problems you can send email to;
175 The current CGEN maintainers are:
177 Doug Evans, Frank Eigler
179 --------- Write After Approval ---------
181 Individuals with "write after approval" have the ability to check in
182 changes, but they must get approval for each change from someone in
183 one of the above lists (blanket write or maintainers).
185 [It's a huge list, folks. You know who you are. If you have the
186 *ability* to do binutils checkins, you're in this group. Just
187 remember to get approval before checking anything in.]
189 ------------- Obvious Fixes -------------
191 Fixes for obvious mistakes do not need approval, and can be checked in
192 right away, but the patch should still be sent to the binutils list.
193 The definition of obvious is a bit hazy, and if you are not sure, then
194 you should seek approval first. Obvious fixes include fixes for
195 spelling mistakes, blatantly incorrect code (where the correct code is
196 also blatantly obvious), and so on. Obvious fixes should always be
197 small, the larger they are, the more likely it is that they contain
198 some un-obvious side effect or consequence.
200 --------- Branch Checkins ---------
202 If a patch is approved for check in to the mainline sources, it can
203 also be checked into the current release branch. Normally however
204 only bug fixes should be applied to the branch. New features, new
205 ports, etc, should be restricted to the mainline. (Otherwise the
206 burden of maintaining the branch in sync with the mainline becomes too
207 great). If you are uncertain as to whether a patch is appropriate for
208 the branch, ask the branch maintainer. This is:
210 (cf global maintainers)
212 -------- Testsuites ---------------
214 In general patches to any of the binutils testsuites should be
215 considered generic and sent to the binutils mailing list for
216 approval. Patches to target specific tests are the responsibility the
217 relevant port maintainer(s), and can be approved/checked in by them.
218 Other testsuite patches need the approval of a blanket-write-priveleges
221 -------- Configure patches ----------
223 Patches to the top level configure files (config.sub & config.guess)
224 are not the domain of the binutils project and they cannot be approved
225 by the binutils group. Instead they should be submitted to the config
228 config-patches@gnu.org
230 --------- Creating Branches ---------
232 Anyone with at least write-after-approval access may create a branch
233 to use for their own development purposes. In keeping with FSF
234 policies, all patches applied to such a branch must come from people
235 with appropriate copyright assignments on file. All legal
236 requirements that would apply to any other contribution apply equally
237 to contributions on a branch.
239 Before creating the branch, you should select a name for the branch of
242 binutils-<org>-<name>
244 where "org" is the initials of your organization, or your own initials
245 if you are acting as an individual. For example, for a branch created
246 by The GNUDist Company, "tgc" would be an appropriate choice for
247 "org". It's up to each organization to select an appropriate choice
248 for "name"; some organizations may use more structure than others, so
249 "name" may contain additional hyphens.
251 Suppose that The GNUDist Company was creating a branch to develop a
252 port of Binutils to the FullMonty processor. Then, an appropriate
253 choice of branch name would be:
257 A date stamp is not required as part of the name field, but some
258 organizations like to have one. If you do include the date, you
259 should follow these rules:
261 1. The date should be the date that the branch was created.
263 2. The date should be numerical and in the form YYYYMMDD.
267 binutils-tgc-fm_20050101
269 would be appropriate if the branch was created on January 1st, 2005.
271 Having selected the branch name, create the branch as follows:
273 1. Check out binutils, so that you have a git checkout corresponding
274 to the initial state of your branch.
278 git tag binutils-<org>-<name>-branchpoint
280 That tag will allow you, and others, to easily determine what's
281 changed on the branch relative to the initial state.
283 3. Create and push the branch:
285 git checkout -b binutils-<org>-<name>-branch
288 4. Document the branch:
290 Add a description of the branch to binutils/BRANCHES, and check
291 that file in. All branch descriptions should be added to the
292 HEAD revision of the file; it doesn't help to modify
293 binutils/BRANCHES on a branch!
295 Please do not commit any patches to a branch you did not create
296 without the explicit permission of the person who created the branch.
298 Copyright (C) 2012-2018 Free Software Foundation, Inc.
300 Copying and distribution of this file, with or without modification,
301 are permitted in any medium without royalty provided the copyright
302 notice and this notice are preserved.
projects / deliverable / binutils-gdb.git / blob