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 <denisc@overta.ru>
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 H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com>
83 HPPA Dave Anglin <dave.anglin@nrc.ca>
84 HPPA elf32 Alan Modra <amodra@gmail.com>
85 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only]
86 IA-64 Jim Wilson <wilson@tuliptree.org>
87 IQ2000 Stan Cox <scox@redhat.com>
88 i860 Jason Eckhardt <jle@rice.edu>
89 ix86 H.J. Lu <hjl.tools@gmail.com>
90 ix86 PE Christopher Faylor <me+binutils@cgf.cx>
91 ix86 COFF DJ Delorie <dj@redhat.com>
92 ix86 PE/COFF Dave Korn <dave.korn.cygwin@gmail.com>
93 ix86 INTEL MODE Jan Beulich <jbeulich@novell.com>
94 LM32 Jon Beniston <jon@beniston.com>
95 M32R Doug Evans <dje@sebabeach.org>
96 M68HC11 M68HC12 Stephane Carrez <Stephane.Carrez@gmail.com>
97 M68HC11 M68HC12 Sean Keys <skeys@ipdatasys.com>
98 M88k Mark Kettenis <kettenis@gnu.org>
99 MACH-O Tristan Gingold <gingold@adacore.com>
100 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com>
101 MEP Dave Brolley <brolley@redhat.com>
102 MICROBLAZE Michael Eager <eager@eagercon.com>
103 MIPS Eric Christopher <echristo@apple.com>
104 MMIX Hans-Peter Nilsson <hp@bitrange.com>
105 MN10300 Eric Christopher <echristo@apple.com>
106 MN10300 Alexandre Oliva <aoliva@redhat.com>
107 Moxie Anthony Green <green@moxielogic.com>
108 MSP430 Dmitry Diky <diwil@spec.ru>
109 NetBSD support Matt Thomas <matt@netbsd.org>
110 PPC Geoff Keating <geoffk@geoffk.org>
111 PPC Alan Modra <amodra@gmail.com>
112 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
113 RL78 DJ Delorie <dj@redhat.com>
114 RX DJ Delorie <dj@redhat.com>
115 RX Nick Clifton <nickc@redhat.com>
116 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
117 SCORE Mei Ligang <ligang@sunnorth.com.cn>
118 SH Alexandre Oliva <aoliva@redhat.com>
119 SH Kaz Kojima <kkojima@rr.iij4u.or.jp>
120 SPARC David S. Miller <davem@davemloft.net>
121 SPU Alan Modra <amodra@gmail.com>
122 TIC4X Svein Seldal <svein@dev.seldal.com>
123 TIC54X Timothy Wall <twall@alum.mit.edu>
124 TIC6X Joseph Myers <joseph@codesourcery.com>
125 TILE-Gx Walter Lee <walt@tilera.com>
126 TILEPro Walter Lee <walt@tilera.com>
127 VAX Matt Thomas <matt@netbsd.org>
128 VAX Jan-Benedict Glaw <jbglaw@lug-owl.de>
129 VMS Tristan Gingold <gingold@adacore.com>
130 x86_64 Jan Hubicka <jh@suse.cz>
131 x86_64 Andreas Jaeger <aj@suse.de>
132 x86_64 H.J. Lu <hjl.tools@gmail.com>
133 XCOFF Richard Sandiford <r.sandiford@uk.ibm.com>
134 XGATE Sean Keys <skeys@ipdatasys.com>
135 Xtensa Sterling Augustine <augustine.sterling@gmail.com>
136 z80 Arnold Metselaar <arnold.metselaar@planet.nl>
137 z8k Christian Groessler <chris@groessler.org>
140 --------- CGEN Maintainers -------------
142 CGEN is a tool for building, amongst other things, assemblers,
143 disassemblers and simulators from a single description of a CPU.
144 It creates files in several of the binutils directories, but it
145 is mentioned here since there is a single group that maintains
146 CGEN and the files that it creates.
148 If you have CGEN related problems you can send email to;
152 The current CGEN maintainers are:
154 Doug Evans, Frank Eigler
156 --------- Write After Approval ---------
158 Individuals with "write after approval" have the ability to check in
159 changes, but they must get approval for each change from someone in
160 one of the above lists (blanket write or maintainers).
162 [It's a huge list, folks. You know who you are. If you have the
163 *ability* to do binutils checkins, you're in this group. Just
164 remember to get approval before checking anything in.]
166 ------------- Obvious Fixes -------------
168 Fixes for obvious mistakes do not need approval, and can be checked in
169 right away, but the patch should still be sent to the binutils list.
170 The definition of obvious is a bit hazy, and if you are not sure, then
171 you should seek approval first. Obvious fixes include fixes for
172 spelling mistakes, blatantly incorrect code (where the correct code is
173 also blatantly obvious), and so on. Obvious fixes should always be
174 small, the larger they are, the more likely it is that they contain
175 some un-obvious side effect or consequence.
177 --------- Branch Checkins ---------
179 If a patch is approved for check in to the mainline sources, it can
180 also be checked into the current release branch. Normally however
181 only bug fixes should be applied to the branch. New features, new
182 ports, etc, should be restricted to the mainline. (Otherwise the
183 burden of maintaining the branch in sync with the mainline becomes too
184 great). If you are uncertain as to whether a patch is appropriate for
185 the branch, ask the branch maintainer. This is:
187 Tristan Gingold <gingold@adacore.com>
189 -------- Testsuites ---------------
191 In general patches to any of the binutils testsuites should be
192 considered generic and sent to the binutils mailing list for
193 approval. Patches to target specific tests are the responsibility the
194 relevent port maintainer(s), and can be approved/checked in by them.
195 Other testsuite patches need the approval of a blanket-write-priveleges
198 -------- Configure patches ----------
200 Patches to the top level configure files (config.sub & config.guess)
201 are not the domain of the binutils project and they cannot be approved
202 by the binutils group. Instead they should be submitted to the config
205 config-patches@gnu.org
207 --------- Creating Branches ---------
209 Anyone with at least write-after-approval access may create a branch
210 to use for their own development purposes. In keeping with FSF
211 policies, all patches applied to such a branch must come from people
212 with appropriate copyright assignments on file. All legal
213 requirements that would apply to any other contribution apply equally
214 to contributions on a branch.
216 Before creating the branch, you should select a name for the branch of
219 binutils-<org>-<name>
221 where "org" is the initials of your organization, or your own initials
222 if you are acting as an individual. For example, for a branch created
223 by The GNUDist Company, "tgc" would be an appropriate choice for
224 "org". It's up to each organization to select an appropriate choice
225 for "name"; some organizations may use more structure than others, so
226 "name" may contain additional hyphens.
228 Suppose that The GNUDist Company was creating a branch to develop a
229 port of Binutils to the FullMonty processor. Then, an appropriate
230 choice of branch name would be:
234 A date stamp is not required as part of the name field, but some
235 organizations like to have one. If you do include the date, you
236 should follow these rules:
238 1. The date should be the date that the branch was created.
240 2. The date should be numerical and in the form YYYYMMDD.
244 binutils-tgc-fm_20050101
246 would be appropriate if the branch was created on January 1st, 2005.
248 Having selected the branch name, create the branch as follows:
250 1. Check out binutils, so that you have a CVS checkout corresponding
251 to the initial state of your branch.
255 cvs tag binutils-<org>-<name>-branchpoint
257 That tag will allow you, and others, to easily determine what's
258 changed on the branch relative to the initial state.
260 3. Create the branch:
262 cvs rtag -b -r binutils-<org>-<name>-branchpoint \
263 binutils-<org>-<name>-branch
265 4. Document the branch:
267 Add a description of the branch to binutils/BRANCHES, and check
268 that file in. All branch descriptions should be added to the
269 HEAD revision of the file; it doesn't help to modify
270 binutils/BRANCHES on a branch!
272 Please do not commit any patches to a branch you did not create
273 without the explicit permission of the person who created the branch.
275 Copyright (C) 2012 Free Software Foundation, Inc.
277 Copying and distribution of this file, with or without modification,
278 are permitted in any medium without royalty provided the copyright
279 notice and this notice are preserved.
projects / deliverable / binutils-gdb.git / blob