]> Git Repo - binutils.git/blame - binutils/MAINTAINERS
Fix xcalloc() calls so order of arguments is not reversed.
[binutils.git] / binutils / MAINTAINERS
CommitLineData
302ab118
DD
1 ========= Binutils Maintainers =========
2
3This is the list of individuals responsible for maintenance and update
1b577b00
NC
4of the GNU Binary Utilities project. This includes the linker (ld),
5the assembler (gas), the profiler (gprof), a whole suite of other
6programs (binutils) and the libraries that they use (bfd and
7opcodes). This project shares a common set of header files with the
8GCC and GDB projects (include), so maintainership of those files is
9shared amoungst the projects.
302ab118 10
1b577b00 11The home page for binutils is:
8c2bc687 12
1b577b00
NC
13 http://www.gnu.org/software/binutils/binutils.html
14
15and patches should be sent to:
16
1f554c69 17 [email protected]
1b577b00
NC
18
19with "[Patch]" as part of the subject line. Note - patches to the
20top level configure.in and config.sub scripts should be sent to:
302ab118 21
1b577b00 22 [email protected]
302ab118 23
1b577b00
NC
24and not to the binutils list.
25
26 --------- Blanket Write Privs ---------
302ab118 27
1b577b00
NC
28The following people have permission to check patches into the
29repository without obtaining approval first:
30
31 Nick Clifton <[email protected]> (head maintainer)
32 Richard Henderson <[email protected]>
33 Ian Taylor <[email protected]>
34 Jeff Law <[email protected]>
35 Jim Wilson <[email protected]>
36 DJ Delorie <[email protected]>
37 Alan Modra <[email protected]>
38 Michael Meissner <[email protected]>
39
40 --------- Maintainers ---------
41
42Maintainers are individuals who are responsible for, and have
43permission to check in changes in, certain subsets of the code. Note
44that maintainers still need approval to check in changes outside of
45the immediate domain that they maintain.
302ab118
DD
46
47If there is no maintainer for a given domain then the responsibility
1b577b00
NC
48falls to the head maintainer (above). If there are several
49maintainers for a given domain then responsibility falls to the first
50maintainer. The first maintainer is free to devolve that
51responsibility among the other maintainers.
52
8db76d70 53 ARC Peter Targett <[email protected]>
1b577b00 54 ARM Nick Clifton <[email protected]>
3a7e524e 55 ARM Richard Earnshaw <[email protected]>
1b577b00
NC
56 AVR Denis Chertykov <[email protected]>
57 CRIS Hans-Peter Nilsson <[email protected]>
58 DWARF2 Jason Merrill <[email protected]>
59 HPPA elf32 Alan Modra <[email protected]>
60 IA64 Jim Wilson <[email protected]>
61 x86_64 Jan Hubicka <[email protected]>
62 x86_64 Andreas Jaeger <[email protected]>
63 i860 Jason Eckhardt <[email protected]>
64 ix86 Alan Modra <[email protected]>
65 ix86 COFF,PE DJ Delorie <[email protected]>
66 ix86 H.J.Lu <[email protected]>
67 ix86 INTEL MODE Diego Novillo <[email protected]>
68 M68HC11 M68HC12 Stephane Carrez <[email protected]>
69 MN10300 Eric Christopher <[email protected]>
70 MIPS Eric Christopher <[email protected]>
71 M88k Ben Elliston <[email protected]>
9b19141a 72 MMIX Hans-Peter Nilsson <[email protected]>
1b577b00 73 PPC Geoff Keating <[email protected]>
c05b685b 74 PPC XCOFF Tom Rix <[email protected]>
54589086 75 s390, s390x Martin Schwidefsky <[email protected]>
6e917903 76