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