aboutsummaryrefslogtreecommitdiff
path: root/binutils/MAINTAINERS
blob: 0055324988212d3b94ddc15f78e91ef8e41569d1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
		========= Binutils Maintainers =========

This is the list of individuals responsible for maintenance and update
of the GNU Binary Utilities project.  This includes the linker (ld),
the assembler (gas), the profiler (gprof), a whole suite of other
programs (binutils) and the libraries that they use (bfd and
opcodes).  This project shares a common set of header files with the
GCC and GDB projects (include), so maintainership of those files is 
shared amoungst the projects.

The home page for binutils is:

  http://www.gnu.org/software/binutils/binutils.html

and patches should be sent to:

  bug-binutils@gnu.org
  
with "[Patch]" as part of the subject line.  Note - patches to the
top level configure.in and config.sub scripts should be sent to:

  config-patches@gnu.org

and not to the binutils list.

		--------- Blanket Write Privs ---------

The following people have permission to check patches into the
repository without obtaining approval first:
		
  Nick Clifton <nickc@redhat.com> (head maintainer)
  Richard Henderson <rth@redhat.com>
  Ian Taylor <ian@zembu.com>
  Jeff Law <law@redhat.com>
  Jim Wilson <wilson@redhat.com>
  DJ Delorie <dj@redhat.com>
  Alan Modra <amodra@bigpond.net.au>
  Michael Meissner <meissner@redhat.com>

      --------- Maintainers ---------

Maintainers are individuals who are responsible for, and have
permission to check in changes in, certain subsets of the code.  Note
that maintainers still need approval to check in changes outside of
the immediate domain that they maintain.

If there is no maintainer for a given domain then the responsibility
falls to the head maintainer (above).  If there are several
maintainers for a given domain then responsibility falls to the first
maintainer.  The first maintainer is free to devolve that
responsibility among the other maintainers.

  ALPHA            Richard Henderson <rth@redhat.com>
  ARC		   Peter Targett <peter.targett@arc.com>
  ARM		   Nick Clifton <nickc@redhat.com>
  ARM		   Richard Earnshaw <rearnsha@arm.com>
  AVR		   Denis Chertykov <denisc@overta.ru>
  AVR		   Marek Michalkiewicz <marekm@amelek.gda.pl>
  CONFIGURE	   Ben Elliston <bje@redhat.com>
  CRIS		   Hans-Peter Nilsson <hp@axis.com>
  DWARF2	   Jason Merrill <jason@redhat.com>
  FR30		   Dave Brolley <brolley@redhat.com>
  FRV		   Dave Brolley <brolley@redhat.com>
  HPPA elf32	   Alan Modra <amodra@bigpond.net.au>
  HPPA elf64	   Jeff Law <law@redhat.com> [Basic maintainance only]
  HPPA		   Dave Anglin <dave.anglin@nrc.ca>
  IA64		   Jim Wilson <wilson@redhat.com>
  i860		   Jason Eckhardt <jle@redhat.com>
  ix86		   Alan Modra <amodra@bigpond.net.au>
  ix86 COFF,PE	   DJ Delorie <dj@redhat.com>
  ix86		   H.J.Lu <hjl@gnu.org>
  ix86 INTEL MODE  Diego Novillo <dnovillo@redhat.com>
  M68HC11 M68HC12  Stephane Carrez <stcarrez@nerim.fr>
  M68k		   Ben Elliston <bje@redhat.com>
  M88k		   Ben Elliston <bje@redhat.com>
  MIPS		   Eric Christopher <echristo@redhat.com>
  MMIX		   Hans-Peter Nilsson <hp@bitrange.com>
  MN10300	   Eric Christopher <echristo@redhat.com>
  MN10300	   Alexandre Oliva <aoliva@redhat.com>
  PPC		   Geoff Keating <geoffk@geoffk.org>
  s390, s390x	   Martin Schwidefsky <schwidefsky@de.ibm.com>
  SH		   Jörn Rennecke <joern.rennecke@superh.com>
  SH		   Alexandre Oliva <aoliva@redhat.com>
  SH		   Kaz Kojima <kkojima@rr.iij4u.or.jp>
  SPARC		   Jakub Jelinek <jakub@redhat.com>
  TESTSUITES	   Ben Elliston <bje@redhat.com>
  TIC54X           Timothy Wall <twall@alum.mit.edu>
  VAX		   Jason R Thorpe <thorpej@wasabisystems.com>
  x86_64	   Jan Hubicka <jh@suse.cz>
  x86_64	   Andreas Jaeger <aj@suse.de>
  z8k		   Christian Groessler <chris@groessler.org>


      --------- CGEN Maintainers -------------

CGEN is a tool for building, amongst other things, assemblers,
disassemblers and simulators from a single description of a CPU.
It creates files in several of the binutils directories, but it
is mentioned here since there is a single group that maintains
CGEN and the files that it creates. 

If you have CGEN related problems you can send email to;

   cgen@sources.redhat.com

The current CGEN maintainers are:

  Doug Evans, Ben Elliston, Frank Eigler

     --------- Write After Approval ---------

Individuals with "write after approval" have the ability to check in
changes, but they must get approval for each change from someone in
one of the above lists (blanket write or maintainers).

[It's a huge list, folks.  You know who you are.  If you have the
 *ability* to do binutils checkins, you're in this group.  Just
 remember to get approval before checking anything in.]

     -------------  Obvious Fixes -------------

Fixes for obvious mistakes do not need approval, and can be checked in
right away, but the patch should still be sent to the binutils list.
The definition of obvious is a bit hazy, and if you are not sure, then
you should seek approval first.  Obvious fixes include fixes for
spelling mistakes, blatantly incorrect code (where the correct code is
also blatantly obvious), and so on.  Obvious fixes should always be
small, the larger they are, the more likely it is that they contain
some un-obvious side effect or consequence.

    --------- Branch Checkins ---------

If a patch is approved for check in to the mainline sources, it can
also be checked into the current release branch.  Normally however
only bug fixes should be applied to the branch.  New features, new
ports, etc, should be restricted to the mainline.  (Otherwise the
burden of maintaining the branch in sync with the mainline becomes too 
great).  If you are uncertain as to whether a patch is appropriate for
the branch, ask the branch maintainer.  This is:

   Daniel Jacobowitz  <dan@debian.org>

    -------- Testsuites ---------------

In general patches to any of the binutils testsuites should be
considered generic and sent to the binutils mailing list for
approval.  Patches to target specific tests are the responsibility the
relevent port maintainer(s), and can be approved/checked in by them.
Other testsuite patches need the approval of a blanket-write-priveleges
person.

    -------- Configure patches ----------

Patches to the top level configure files (config.sub & config.guess)
are not the domain of the binutils project and they cannot be approved
by the binutils group.  Instead they should be submitted to the config
maintainer at:

	config-patches@gnu.org