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:
19 with "[Patch]" as part of the subject line. Note - patches to the
20 top level configure.in and config.sub scripts should be sent to:
22 config-patches@gnu.org
24 and not to the binutils list.
26 --------- Blanket Write Privs ---------
28 The following people have permission to check patches into the
29 repository without obtaining approval first:
31 Nick Clifton <nickc@redhat.com> (head maintainer)
32 Richard Henderson <rth@redhat.com>
33 Ian Taylor <ian@zembu.com>
34 Jeff Law <law@redhat.com>
35 Jim Wilson <wilson@redhat.com>
36 DJ Delorie <dj@redhat.com>
37 Alan Modra <amodra@bigpond.net.au>
38 Michael Meissner <meissner@redhat.com>
40 --------- Maintainers ---------
42 Maintainers are individuals who are responsible for, and have
43 permission to check in changes in, certain subsets of the code. Note
44 that maintainers still need approval to check in changes outside of
45 the immediate domain that they maintain.
47 If there is no maintainer for a given domain then the responsibility
48 falls to the head maintainer (above). If there are several
49 maintainers for a given domain then responsibility falls to the first
50 maintainer. The first maintainer is free to devolve that
51 responsibility among the other maintainers.
53 ARC Peter Targett <peter.targett@arccores.com>
54 ARM Nick Clifton <nickc@redhat.com>
55 ARM Richard Earnshaw <rearnsha@arm.com>
56 AVR Denis Chertykov <denisc@overta.ru>
57 CRIS Hans-Peter Nilsson <hp@axis.com>
58 DWARF2 Jason Merrill <jason@redhat.com>
59 HPPA elf32 Alan Modra <amodra@bigpond.net.au>
60 IA64 Jim Wilson <wilson@redhat.com>
61 x86_64 Jan Hubicka <jh@suse.cz>
62 x86_64 Andreas Jaeger <aj@suse.de>
63 i860 Jason Eckhardt <jle@redhat.com>
64 ix86 Alan Modra <amodra@bigpond.net.au>
65 ix86 COFF,PE DJ Delorie <dj@redhat.com>
66 ix86 H.J.Lu <hjl@gnu.org>
67 ix86 INTEL MODE Diego Novillo <dnovillo@redhat.com>
68 M68HC11 M68HC12 Stephane Carrez <Stephane.Carrez@worldnet.fr>
69 MN10300 Eric Christopher <echristo@redhat.com>
70 MN10300 Alexandre Oliva <aoliva@redhat.com>
71 MIPS Eric Christopher <echristo@redhat.com>
72 M88k Ben Elliston <bje@redhat.com>
73 MMIX Hans-Peter Nilsson <hp@bitrange.com>
74 PPC Geoff Keating <geoffk@redhat.com>
75 PPC XCOFF Tom Rix <trix@redhat.com>
76 s390, s390x Martin Schwidefsky <schwidefsky@de.ibm.com>
77 SH J�örn Rennecke <amylaar@onetel.net.uk>
78 SH Hans-Peter Nilsson <hp@bitrange.com>
79 SH Alexandre Oliva <aoliva@redhat.com>
80 SPARC Jakub Jelinek <jakub@redhat.com>
81 TIC54X Timothy Wall <twall@alum.mit.edu>
82 z8k Christian Groessler <cpg@aladdin.de>
84 --------- CGEN Maintainers -------------
86 CGEN is a tool for building, amongst other things, assemblers,
87 disassemblers and simulators from a single description of a CPU.
88 It creates files in several of the binutils directories, but it
89 is mentioned here since there is a single group that maintains
90 CGEN and the files that it creates.
92 If you have CGEN related problems you can send email to;
94 cgen@sources.redhat.com
96 The current CGEN maintainers are:
98 Doug Evans, Ben Elliston, Frank Eigler
100 --------- Write After Approval ---------
102 Individuals with "write after approval" have the ability to check in
103 changes, but they must get approval for each change from someone in
104 one of the above lists (blanket write or maintainers).
106 [It's a huge list, folks. You know who you are. If you have the
107 *ability* to do binutils checkins, you're in this group. Just
108 remember to get approval before checking anything in.]
110 ------------- Obvious Fixes -------------
112 Fixes for obvious mistakes do not need approval, and can be checked in
113 right away, but the patch should still be sent to the binutils list.
114 The definition of obvious is a bit hazy, and if you are not sure, then
115 you should seek approval first. Obvious fixes include fixes for
116 spelling mistakes, blatantly incorrect code (where the correct code is
117 also blatantly obvious), and so on. Obvious fixes should always be
118 small, the larger they are, the more likely it is that they contain
119 some un-obvious side effect or consequence.
121 --------- Branch Checkins ---------
123 If a patch is approved for check in to the mainline sources, it can
124 also be checked into the current release branch. Normally however
125 only bug fixes should be applied to the branch. New features, new
126 ports, etc, should be restricted to the mainline. (Otherwise the
127 burden of maintaining the branch in sync with the mainline becomes too
128 great). If you are uncertain as to whether a patch is appropriate for
129 the branch, ask the branch maintainer. This is:
131 Daniel Jacobowitz <dan@debian.org>