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.in, 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 --------- Blanket Write Privs ---------
32 The following people have permission to check patches into the
33 repository without obtaining approval first:
35 Nick Clifton <nickc@redhat.com> (head maintainer)
36 Richard Henderson <rth@redhat.com>
37 Ian Lance Taylor <ian@airs.com>
38 Jeff Law <law@redhat.com>
39 Jim Wilson <wilson@tuliptree.org>
40 DJ Delorie <dj@redhat.com>
41 Alan Modra <amodra@gmail.com>
42 Michael Meissner <gnu@the-meissners.org>
43 Daniel Jacobowitz <drow@false.org>
44 Richard Sandiford <rdsandiford@googlemail.com>
46 --------- Maintainers ---------
48 Maintainers are individuals who are responsible for, and have
49 permission to check in changes in, certain subsets of the code. Note
50 that maintainers still need approval to check in changes outside of
51 the immediate domain that they maintain.
53 If there is no maintainer for a given domain then the responsibility
54 falls to the head maintainer (above). If there are several
55 maintainers for a given domain then responsibility falls to the first
56 maintainer. The first maintainer is free to devolve that
57 responsibility among the other maintainers.
59 ALPHA Richard Henderson <rth@redhat.com>
60 AARCH64 Richard Earnshaw <rearnsha@arm.com>
61 AARCH64 Marcus Shawcroft <marcus.shawcroft@arm.com>
62 ARM Nick Clifton <nickc@redhat.com>
63 ARM Richard Earnshaw <rearnsha@arm.com>
64 ARM Paul Brook <paul@codesourcery.com>
65 ARM (Symbian) Mark Mitchell <mark@codesourcery.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 Bernd Schmidt <bernd.schmidt@analog.com>
70 BFIN Mike Frysinger <michael.frysinger@analog.com>
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 EPIPHANY Joern Rennecke <joern.rennecke@embecosm.com>
79 FR30 Dave Brolley <brolley@redhat.com>
80 FRV Dave Brolley <brolley@redhat.com>
81 FRV Alexandre Oliva <aoliva@redhat.com>
82 GOLD Ian Lance Taylor <iant@google.com>
83 GOLD Cary Coutant <ccoutant@google.com>
84 H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com>
85 HPPA Dave Anglin <dave.anglin@nrc.ca>
86 HPPA elf32 Alan Modra <amodra@gmail.com>
87 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only]
88 IA-64 Jim Wilson <wilson@tuliptree.org>
89 IQ2000 Stan Cox <scox@redhat.com>
90 i860 Jason Eckhardt <jle@rice.edu>
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 M88k Mark Kettenis <kettenis@gnu.org>
101 MACH-O Tristan Gingold <gingold@adacore.com>
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 Eric Christopher <echristo@apple.com>
107 MMIX Hans-Peter Nilsson <hp@bitrange.com>
108 MN10300 Eric Christopher <echristo@apple.com>
109 MN10300 Alexandre Oliva <aoliva@redhat.com>
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 PPC Geoff Keating <geoffk@geoffk.org>
120 PPC Alan Modra <amodra@gmail.com>
121 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
122 RL78 DJ Delorie <dj@redhat.com>
123 RX DJ Delorie <dj@redhat.com>
124 RX Nick Clifton <nickc@redhat.com>
125 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
126 SCORE Mei Ligang <ligang@sunnorth.com.cn>
127 SH Alexandre Oliva <aoliva@redhat.com>
128 SH Kaz Kojima <kkojima@rr.iij4u.or.jp>
129 SPARC David S. Miller <davem@davemloft.net>
130 SPU Alan Modra <amodra@gmail.com>
131 TIC4X Svein Seldal <svein@dev.seldal.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 VMS Tristan Gingold <gingold@adacore.com>
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>
149 --------- CGEN Maintainers -------------
151 CGEN is a tool for building, amongst other things, assemblers,
152 disassemblers and simulators from a single description of a CPU.
153 It creates files in several of the binutils directories, but it
154 is mentioned here since there is a single group that maintains
155 CGEN and the files that it creates.
157 If you have CGEN related problems you can send email to;
161 The current CGEN maintainers are:
163 Doug Evans, Frank Eigler
165 --------- Write After Approval ---------
167 Individuals with "write after approval" have the ability to check in
168 changes, but they must get approval for each change from someone in
169 one of the above lists (blanket write or maintainers).
171 [It's a huge list, folks. You know who you are. If you have the
172 *ability* to do binutils checkins, you're in this group. Just
173 remember to get approval before checking anything in.]
175 ------------- Obvious Fixes -------------
177 Fixes for obvious mistakes do not need approval, and can be checked in
178 right away, but the patch should still be sent to the binutils list.
179 The definition of obvious is a bit hazy, and if you are not sure, then
180 you should seek approval first. Obvious fixes include fixes for
181 spelling mistakes, blatantly incorrect code (where the correct code is
182 also blatantly obvious), and so on. Obvious fixes should always be
183 small, the larger they are, the more likely it is that they contain
184 some un-obvious side effect or consequence.
186 --------- Branch Checkins ---------
188 If a patch is approved for check in to the mainline sources, it can
189 also be checked into the current release branch. Normally however
190 only bug fixes should be applied to the branch. New features, new
191 ports, etc, should be restricted to the mainline. (Otherwise the
192 burden of maintaining the branch in sync with the mainline becomes too
193 great). If you are uncertain as to whether a patch is appropriate for
194 the branch, ask the branch maintainer. This is:
196 Tristan Gingold <gingold@adacore.com>
198 -------- Testsuites ---------------
200 In general patches to any of the binutils testsuites should be
201 considered generic and sent to the binutils mailing list for
202 approval. Patches to target specific tests are the responsibility the
203 relevent port maintainer(s), and can be approved/checked in by them.
204 Other testsuite patches need the approval of a blanket-write-priveleges
207 -------- Configure patches ----------
209 Patches to the top level configure files (config.sub & config.guess)
210 are not the domain of the binutils project and they cannot be approved
211 by the binutils group. Instead they should be submitted to the config
214 config-patches@gnu.org
216 --------- Creating Branches ---------
218 Anyone with at least write-after-approval access may create a branch
219 to use for their own development purposes. In keeping with FSF
220 policies, all patches applied to such a branch must come from people
221 with appropriate copyright assignments on file. All legal
222 requirements that would apply to any other contribution apply equally
223 to contributions on a branch.
225 Before creating the branch, you should select a name for the branch of
228 binutils-<org>-<name>
230 where "org" is the initials of your organization, or your own initials
231 if you are acting as an individual. For example, for a branch created
232 by The GNUDist Company, "tgc" would be an appropriate choice for
233 "org". It's up to each organization to select an appropriate choice
234 for "name"; some organizations may use more structure than others, so
235 "name" may contain additional hyphens.
237 Suppose that The GNUDist Company was creating a branch to develop a
238 port of Binutils to the FullMonty processor. Then, an appropriate
239 choice of branch name would be:
243 A date stamp is not required as part of the name field, but some
244 organizations like to have one. If you do include the date, you
245 should follow these rules:
247 1. The date should be the date that the branch was created.
249 2. The date should be numerical and in the form YYYYMMDD.
253 binutils-tgc-fm_20050101
255 would be appropriate if the branch was created on January 1st, 2005.
257 Having selected the branch name, create the branch as follows:
259 1. Check out binutils, so that you have a git checkout corresponding
260 to the initial state of your branch.
264 git tag binutils-<org>-<name>-branchpoint
266 That tag will allow you, and others, to easily determine what's
267 changed on the branch relative to the initial state.
269 3. Create and push the branch:
271 git checkout -b binutils-<org>-<name>-branch
274 4. Document the branch:
276 Add a description of the branch to binutils/BRANCHES, and check
277 that file in. All branch descriptions should be added to the
278 HEAD revision of the file; it doesn't help to modify
279 binutils/BRANCHES on a branch!
281 Please do not commit any patches to a branch you did not create
282 without the explicit permission of the person who created the branch.
284 Copyright (C) 2012-2015 Free Software Foundation, Inc.
286 Copying and distribution of this file, with or without modification,
287 are permitted in any medium without royalty provided the copyright
288 notice and this notice are preserved.
projects / deliverable / binutils-gdb.git / blob