2000-08-03 H.J. Lu <hjl@gnu.org>
[deliverable/binutils-gdb.git] / binutils / MAINTAINERS
CommitLineData
302ab118
DD
1 ========= Binutils Maintainers =========
2
3This is the list of individuals responsible for maintenance and update
4of the "binutils" module, which includes the bfd, binutils, include,
5gas, gprof, ld, and opcodes subdirectories. The home page for binutils
6is http://sourceware.cygnus.com/binutils/ and patches should be sent to
7binutils@sourceware.cygnus.com with "[patch]" as part of the subject.
8
9 --------- Blanket Write Privs ---------
10
11Nick Clifton <nickc@redhat.com> (head maintainer)
12Richard Henderson <rth@redhat.com>
13Ian Taylor <ian@zembu.com>
14Jeff Law <law@redhat.com>
15Jim Wilson <wilson@redhat.com>
16DJ Delorie <dj@redhat.com>
17Alan Modra <alan@linuxcare.com.au>
68dcecab 18Michael Meissner <meissner@redhat.com>
302ab118
DD
19
20 --------- Maintainers ---------
21
22Maintainers are individuals who are responsible for, and have permission
23to check in changes in, certain subsets of the code. Note that
24maintainers still need approval to check in changes outside of the
25immediate domain that they maintain.
26
27If there is no maintainer for a given domain then the responsibility
28falls to the head maintainer (above). If there are several maintainers
29for a given domain then responsibility falls to the first maintainer.
30The first maintainer is free to devolve that responsibility among the
31other maintainers.
32
3316ae25
NC
33ARM Nick Clifton <nickc@redhat.com>
34AVR Denis Chertykov <denisc@overta.ru>
1b61cf92 35CRIS Hans-Peter Nilsson <hp@axis.com>
3316ae25 36HPPA elf32 Alan Modra <alan@linuxcare.com.au>
878d476a 37i860 Jason Eckhardt <jle@redhat.com>
3316ae25
NC
38ix86 Alan Modra <alan@linuxcare.com.au>
39ix86 COFF,PE DJ Delorie <dj@redhat.com>
40ix86 H.J.Lu <hjl@gnu.org>
302ab118
DD
41MIPS Ulf Carlsson <ulfc@calypso.engr.sgi.com>
42PPC Geoff Keating <geoffk@redhat.com>
cfd22345 43SPARC Jakub Jelinek <jakub@redhat.com>
3316ae25 44
302ab118
DD
45
46 --------- Write After Approval ---------
47
48Individuals with "write after approval" have the ability to check in
49changes, but they must get approval for each change from someone in
50one of the above lists (blanket write or maintainers).
51
52[It's a huge list, folks. You know who you are. If you have the
53 *ability* to do binutils checkins, you're in this group. Just remember
54 to get approval before checking anything in.]
This page took 0.02735 seconds and 4 git commands to generate.