| blob | b856292efa270a8612cb9084c5f25becd9b322b5 |
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 bug-binutils@gnu.org or binutils@sources.redhat.com
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@sources.redhat.com).
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@specifixinc.com>
40 DJ Delorie <dj@redhat.com>
41 Alan Modra <amodra@bigpond.net.au>
42 Michael Meissner <gnu@the-meissners.org>
43 Daniel Jacobowitz <dan@debian.org>
45 --------- Maintainers ---------
47 Maintainers are individuals who are responsible for, and have
48 permission to check in changes in, certain subsets of the code. Note
49 that maintainers still need approval to check in changes outside of
50 the immediate domain that they maintain.
52 If there is no maintainer for a given domain then the responsibility
53 falls to the head maintainer (above). If there are several
54 maintainers for a given domain then responsibility falls to the first
55 maintainer. The first maintainer is free to devolve that
56 responsibility among the other maintainers.
58 ALPHA Richard Henderson <rth@redhat.com>
59 ARM Nick Clifton <nickc@redhat.com>
60 ARM Richard Earnshaw <rearnsha@arm.com>
61 ARM (Symbian) Paul Brook <paul@codesourcery.com>
62 ARM (Symbian) Mark Mitchell <mark@codesourcery.com>
63 AVR Denis Chertykov <denisc@overta.ru>
64 AVR Marek Michalkiewicz <marekm@amelek.gda.pl>
65 BUILD SYSTEM Ben Elliston <bje@gnu.org>
66 BUILD SYSTEM Daniel Jacobowitz <dan@debian.org>
67 CRIS Hans-Peter Nilsson <hp@axis.com>
68 CRX Tomer Levi <Tomer.Levi@nsc.com>
69 DWARF2 Jason Merrill <jason@redhat.com>
70 FR30 Dave Brolley <brolley@redhat.com>
71 FRV Dave Brolley <brolley@redhat.com>
72 FRV Alexandre Oliva <aoliva@redhat.com>
73 HPPA Dave Anglin <dave.anglin@nrc.ca>
74 HPPA elf32 Alan Modra <amodra@bigpond.net.au>
75 HPPA elf64 Jeff Law <law@redhat.com> [Basic maintainance only]
76 IA-64 Jim Wilson <wilson@specifixinc.com>
77 IQ2000 Stan Cox <scox@redhat.com>
78 i860 Jason Eckhardt <jle@rice.edu>
79 ix86 Alan Modra <amodra@bigpond.net.au>
80 ix86 PE Christopher Faylor <cgf@redhat.com>
81 ix86 COFF DJ Delorie <dj@redhat.com>
82 ix86 H.J.Lu <hjl@gnu.org>
83 M68HC11 M68HC12 Stephane Carrez <stcarrez@nerim.fr>
84 M68k Ben Elliston <bje@gnu.org>
85 M88k Mark Kettenis <kettenis@gnu.org>
86 MAXQ Inderpreet Singh <inderpreetb@noida.hcltech.com>
87 MIPS Eric Christopher <echristo@redhat.com>
88 MIPS Thiemo Seufer <seufer@csv.ica.uni-stuttgart.de>
89 MMIX Hans-Peter Nilsson <hp@bitrange.com>
90 MN10300 Eric Christopher <echristo@redhat.com>
91 MN10300 Alexandre Oliva <aoliva@redhat.com>
92 MSP430 Dmitry Diky <diwil@spec.ru>
93 PPC Geoff Keating <geoffk@geoffk.org>
94 PPC vector ext Aldy Hernandez <aldyh@redhat.com>
95 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
96 SH Jörn Rennecke <joern.rennecke@superh.com>
97 SH Alexandre Oliva <aoliva@redhat.com>
98 SH Kaz Kojima <kkojima@rr.iij4u.or.jp>
99 SPARC Jakub Jelinek <jakub@redhat.com>
100 TESTSUITES Ben Elliston <bje@gnu.org>
101 TIC4X Svein Seldal <svein@dev.seldal.com>
102 TIC54X Timothy Wall <twall@alum.mit.edu>
103 VAX Jason R Thorpe <thorpej@netbsd.org>
104 x86_64 Jan Hubicka <jh@suse.cz>
105 x86_64 Andreas Jaeger <aj@suse.de>
106 Xtensa Bob Wilson <bob.wilson@acm.org>
107 z8k Christian Groessler <chris@groessler.org>
110 --------- CGEN Maintainers -------------
112 CGEN is a tool for building, amongst other things, assemblers,
113 disassemblers and simulators from a single description of a CPU.
114 It creates files in several of the binutils directories, but it
115 is mentioned here since there is a single group that maintains
116 CGEN and the files that it creates.
118 If you have CGEN related problems you can send email to;
120 cgen@sources.redhat.com
122 The current CGEN maintainers are:
124 Doug Evans, Ben Elliston, Frank Eigler
126 --------- Write After Approval ---------
128 Individuals with "write after approval" have the ability to check in
129 changes, but they must get approval for each change from someone in
130 one of the above lists (blanket write or maintainers).
132 [It's a huge list, folks. You know who you are. If you have the
133 *ability* to do binutils checkins, you're in this group. Just
134 remember to get approval before checking anything in.]
136 ------------- Obvious Fixes -------------
138 Fixes for obvious mistakes do not need approval, and can be checked in
139 right away, but the patch should still be sent to the binutils list.
140 The definition of obvious is a bit hazy, and if you are not sure, then
141 you should seek approval first. Obvious fixes include fixes for
142 spelling mistakes, blatantly incorrect code (where the correct code is
143 also blatantly obvious), and so on. Obvious fixes should always be
144 small, the larger they are, the more likely it is that they contain
145 some un-obvious side effect or consequence.
147 --------- Branch Checkins ---------
149 If a patch is approved for check in to the mainline sources, it can
150 also be checked into the current release branch. Normally however
151 only bug fixes should be applied to the branch. New features, new
152 ports, etc, should be restricted to the mainline. (Otherwise the
153 burden of maintaining the branch in sync with the mainline becomes too
154 great). If you are uncertain as to whether a patch is appropriate for
155 the branch, ask the branch maintainer. This is:
157 Daniel Jacobowitz <dan@debian.org>
159 -------- Testsuites ---------------
161 In general patches to any of the binutils testsuites should be
162 considered generic and sent to the binutils mailing list for
163 approval. Patches to target specific tests are the responsibility the
164 relevent port maintainer(s), and can be approved/checked in by them.
165 Other testsuite patches need the approval of a blanket-write-priveleges
166 person.
168 -------- Configure patches ----------
170 Patches to the top level configure files (config.sub & config.guess)
171 are not the domain of the binutils project and they cannot be approved
172 by the binutils group. Instead they should be submitted to the config
173 maintainer at:
175 config-patches@gnu.org
177 --------- Creating Branches ---------
179 Anyone with at least write-after-approval access may create a branch
180 to use for their own development purposes. In keeping with FSF
181 policies, all patches applied to such a branch must come from people
182 with appropriate copyright assignments on file. All legal
183 requirements that would apply to any other contribution apply equally
184 to contributions on a branch.
186 Before creating the branch, you should select a name for the branch of
187 the form:
189 binutils-<org>-<name>
191 where "org" is the initials of your organization, or your own initials
192 if you are acting as an individual. For example, for a branch created
193 by The GNUDist Company, "tgc" would be an appropriate choice for
194 "org". It's up to each organization to select an appropriate choice
195 for "name"; some organizations may use more structure than others, so
196 "name" may contain additional hyphens.
198 Suppose that The GNUDist Company was creating a branch to develop a
199 port of Binutils to the FullMonty processor. Then, an appropriate
200 choice of branch name would be:
202 binutils-tgc-fm
204 A data stamp is not required as part of the name field, but some
205 organizations like to have one. If you do include the date, you
206 should follow these rules:
208 1. The date should be the date that the branch was created.
210 2. The date should be numerical and in the form YYYYMMDD.
212 For example:
214 binutils-tgc-fm_20050101
216 would be appropriate if the branch was created on January 1st, 2005.
218 Having selected the branch name, create the branch as follows:
220 1. Check out binutils, so that you have a CVS checkout corresponding
221 to the initial state of your branch.
223 2. Create a tag:
225 cvs tag binutils-<org>-<name>-branchpoint
227 That tag will allow you, and others, to easily determine what's
228 changed on the branch relative to the initial state.
230 3. Create the branch:
232 cvs rtag -b -r binutils-<org>-<name>-branchpoint \
233 binutils-<org>-<name>-branch
235 4. Document the branch:
237 Add a description of the branch to binutils/BRANCHES, and check
238 that file in. All branch descriptions should be added to the
239 HEAD revision of the file; it doesn't help to modify
240 binutils/BRANCHES on a branch!
242 Please do not commit any patches to a branch you did not create
243 without the explicit permission of the person who created the branch.