| blob | 3afc09a3dd3f907155ab4f64e97821d640990f6e |
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 <dan@codesourcery.com>
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 ARM Nick Clifton <nickc@redhat.com>
61 ARM Richard Earnshaw <rearnsha@arm.com>
62 ARM Paul Brook <paul@codesourcery.com>
63 ARM (Symbian) Mark Mitchell <mark@codesourcery.com>
64 AVR Denis Chertykov <denisc@overta.ru>
65 AVR Marek Michalkiewicz <marekm@amelek.gda.pl>
66 BFIN Jie Zhang <jie@codesourcery.com>
67 BFIN Bernd Schmidt <bernd.schmidt@analog.com>
68 BFIN Mike Frysinger <michael.frysinger@analog.com>
69 BUILD SYSTEM Daniel Jacobowitz <dan@codesourcery.com>
70 CR16 M R Swami Reddy <MR.Swami.Reddy@nsc.com>
71 CRIS Hans-Peter Nilsson <hp@axis.com>
72 CRX M R Swami Reddy <MR.Swami.Reddy@nsc.com>
73 DLX Nikolaos Kavvadias <nkavv@physics.auth.gr>
74 DWARF2 Jason Merrill <jason@redhat.com>
75 FR30 Dave Brolley <brolley@redhat.com>
76 FRV Dave Brolley <brolley@redhat.com>
77 FRV Alexandre Oliva <aoliva@redhat.com>
78 H8300 Prafulla Thakare <prafulla.thakare@kpitcummins.com>
79 HPPA Dave Anglin <dave.anglin@nrc.ca>
80 HPPA elf32 Alan Modra <amodra@gmail.com>
81 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only]
82 IA-64 Jim Wilson <wilson@tuliptree.org>
83 IQ2000 Stan Cox <scox@redhat.com>
84 i860 Jason Eckhardt <jle@rice.edu>
85 ix86 H.J. Lu <hjl.tools@gmail.com>
86 ix86 PE Christopher Faylor <me+binutils@cgf.cx>
87 ix86 COFF DJ Delorie <dj@redhat.com>
88 ix86 PE/COFF Dave Korn <dave.korn.cygwin@gmail.com>
89 ix86 INTEL MODE Jan Beulich <jbeulich@novell.com>
90 LM32 Jon Beniston <jon@beniston.com>
91 M32R Doug Evans <dje@sebabeach.org>
92 M68HC11 M68HC12 Stephane Carrez <stcarrez@nerim.fr>
93 M88k Mark Kettenis <kettenis@gnu.org>
94 MACH-O Tristan Gingold <gingold@adacore.com>
95 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com>
96 MEP Dave Brolley <brolley@redhat.com>
97 MICROBLAZE Michael Eager <eager@eagercon.com>
98 MIPS Eric Christopher <echristo@apple.com>
99 MMIX Hans-Peter Nilsson <hp@bitrange.com>
100 MN10300 Eric Christopher <echristo@apple.com>
101 MN10300 Alexandre Oliva <aoliva@redhat.com>
102 Moxie Anthony Green <green@moxielogic.com>
103 MSP430 Dmitry Diky <diwil@spec.ru>
104 NetBSD support Matt Thomas <matt@netbsd.org>
105 PPC Geoff Keating <geoffk@geoffk.org>
106 PPC Alan Modra <amodra@gmail.com>
107 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
108 RX DJ Delorie <dj@redhat.com>
109 RX Nick Clifton <nickc@redhat.com>
110 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
111 SCORE Mei Ligang <ligang@sunnorth.com.cn>
112 SH Alexandre Oliva <aoliva@redhat.com>
113 SH Kaz Kojima <kkojima@rr.iij4u.or.jp>
114 SPARC Jakub Jelinek <jakub@redhat.com>
115 SPU Alan Modra <amodra@gmail.com>
116 TIC4X Svein Seldal <svein@dev.seldal.com>
117 TIC54X Timothy Wall <twall@alum.mit.edu>
118 TIC6X Joseph Myers <joseph@codesourcery.com>
119 VAX Matt Thomas <matt@netbsd.org>
120 VAX Jan-Benedict Glaw <jbglaw@lug-owl.de>
121 VMS Tristan Gingold <gingold@adacore.com>
122 x86_64 Jan Hubicka <jh@suse.cz>
123 x86_64 Andreas Jaeger <aj@suse.de>
124 x86_64 H.J. Lu <hjl.tools@gmail.com>
125 XCOFF Richard Sandiford <r.sandiford@uk.ibm.com>
126 Xtensa Sterling Augustine <sterling@tensilica.com>
127 z80 Arnold Metselaar <arnold.metselaar@planet.nl>
128 z8k Christian Groessler <chris@groessler.org>
131 --------- CGEN Maintainers -------------
133 CGEN is a tool for building, amongst other things, assemblers,
134 disassemblers and simulators from a single description of a CPU.
135 It creates files in several of the binutils directories, but it
136 is mentioned here since there is a single group that maintains
137 CGEN and the files that it creates.
139 If you have CGEN related problems you can send email to;
141 cgen@sourceware.org
143 The current CGEN maintainers are:
145 Doug Evans, Frank Eigler
147 --------- Write After Approval ---------
149 Individuals with "write after approval" have the ability to check in
150 changes, but they must get approval for each change from someone in
151 one of the above lists (blanket write or maintainers).
153 [It's a huge list, folks. You know who you are. If you have the
154 *ability* to do binutils checkins, you're in this group. Just
155 remember to get approval before checking anything in.]
157 ------------- Obvious Fixes -------------
159 Fixes for obvious mistakes do not need approval, and can be checked in
160 right away, but the patch should still be sent to the binutils list.
161 The definition of obvious is a bit hazy, and if you are not sure, then
162 you should seek approval first. Obvious fixes include fixes for
163 spelling mistakes, blatantly incorrect code (where the correct code is
164 also blatantly obvious), and so on. Obvious fixes should always be
165 small, the larger they are, the more likely it is that they contain
166 some un-obvious side effect or consequence.
168 --------- Branch Checkins ---------
170 If a patch is approved for check in to the mainline sources, it can
171 also be checked into the current release branch. Normally however
172 only bug fixes should be applied to the branch. New features, new
173 ports, etc, should be restricted to the mainline. (Otherwise the
174 burden of maintaining the branch in sync with the mainline becomes too
175 great). If you are uncertain as to whether a patch is appropriate for
176 the branch, ask the branch maintainer. This is:
178 Tristan Gingold <gingold@adacore.com>
180 -------- Testsuites ---------------
182 In general patches to any of the binutils testsuites should be
183 considered generic and sent to the binutils mailing list for
184 approval. Patches to target specific tests are the responsibility the
185 relevent port maintainer(s), and can be approved/checked in by them.
186 Other testsuite patches need the approval of a blanket-write-priveleges
187 person.
189 -------- Configure patches ----------
191 Patches to the top level configure files (config.sub & config.guess)
192 are not the domain of the binutils project and they cannot be approved
193 by the binutils group. Instead they should be submitted to the config
194 maintainer at:
196 config-patches@gnu.org
198 --------- Creating Branches ---------
200 Anyone with at least write-after-approval access may create a branch
201 to use for their own development purposes. In keeping with FSF
202 policies, all patches applied to such a branch must come from people
203 with appropriate copyright assignments on file. All legal
204 requirements that would apply to any other contribution apply equally
205 to contributions on a branch.
207 Before creating the branch, you should select a name for the branch of
208 the form:
210 binutils-<org>-<name>
212 where "org" is the initials of your organization, or your own initials
213 if you are acting as an individual. For example, for a branch created
214 by The GNUDist Company, "tgc" would be an appropriate choice for
215 "org". It's up to each organization to select an appropriate choice
216 for "name"; some organizations may use more structure than others, so
217 "name" may contain additional hyphens.
219 Suppose that The GNUDist Company was creating a branch to develop a
220 port of Binutils to the FullMonty processor. Then, an appropriate
221 choice of branch name would be:
223 binutils-tgc-fm
225 A date stamp is not required as part of the name field, but some
226 organizations like to have one. If you do include the date, you
227 should follow these rules:
229 1. The date should be the date that the branch was created.
231 2. The date should be numerical and in the form YYYYMMDD.
233 For example:
235 binutils-tgc-fm_20050101
237 would be appropriate if the branch was created on January 1st, 2005.
239 Having selected the branch name, create the branch as follows:
241 1. Check out binutils, so that you have a CVS checkout corresponding
242 to the initial state of your branch.
244 2. Create a tag:
246 cvs tag binutils-<org>-<name>-branchpoint
248 That tag will allow you, and others, to easily determine what's
249 changed on the branch relative to the initial state.
251 3. Create the branch:
253 cvs rtag -b -r binutils-<org>-<name>-branchpoint \
254 binutils-<org>-<name>-branch
256 4. Document the branch:
258 Add a description of the branch to binutils/BRANCHES, and check
259 that file in. All branch descriptions should be added to the
260 HEAD revision of the file; it doesn't help to modify
261 binutils/BRANCHES on a branch!
263 Please do not commit any patches to a branch you did not create
264 without the explicit permission of the person who created the branch.