1 |
24 |
jeremybenn |
GDB Maintainers
|
2 |
|
|
===============
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
Overview
|
6 |
|
|
--------
|
7 |
|
|
|
8 |
|
|
This file describes different groups of people who are, together, the
|
9 |
|
|
maintainers and developers of the GDB project. Don't worry - it sounds
|
10 |
|
|
more complicated than it really is.
|
11 |
|
|
|
12 |
|
|
There are four groups of GDB developers, covering the patch development and
|
13 |
|
|
review process:
|
14 |
|
|
|
15 |
|
|
- The Global Maintainers.
|
16 |
|
|
|
17 |
|
|
These are the developers in charge of most daily development. They
|
18 |
|
|
have wide authority to apply and reject patches, but defer to the
|
19 |
|
|
Responsible Maintainers (see below) within their spheres of
|
20 |
|
|
responsibility.
|
21 |
|
|
|
22 |
|
|
- The Responsible Maintainers.
|
23 |
|
|
|
24 |
|
|
These are developers who have expertise and interest in a particular
|
25 |
|
|
area of GDB, who are generally available to review patches, and who
|
26 |
|
|
prefer to enforce a single vision within their areas.
|
27 |
|
|
|
28 |
|
|
- The Authorized Committers.
|
29 |
|
|
|
30 |
|
|
These are developers who are trusted to make changes within a specific
|
31 |
|
|
area of GDB without additional oversight.
|
32 |
|
|
|
33 |
|
|
- The Write After Approval Maintainers.
|
34 |
|
|
|
35 |
|
|
These are developers who have write access to the GDB source tree. They
|
36 |
|
|
can check in their own changes once a developer with the appropriate
|
37 |
|
|
authority has approved the changes; they can also apply the Obvious
|
38 |
|
|
Fix Rule (below).
|
39 |
|
|
|
40 |
|
|
All maintainers are encouraged to post major patches to the gdb-patches
|
41 |
|
|
mailing list for comments, even if they have the authority to commit the
|
42 |
|
|
patch without review from another maintainer. This especially includes
|
43 |
|
|
patches which change internal interfaces (e.g. global functions, data
|
44 |
|
|
structures) or external interfaces (e.g. user, remote, MI, et cetera).
|
45 |
|
|
|
46 |
|
|
The term "review" is used in this file to describe several kinds of feedback
|
47 |
|
|
from a maintainer: approval, rejection, and requests for changes or
|
48 |
|
|
clarification with the intention of approving a revised version. Review is
|
49 |
|
|
a privilege and/or responsibility of various positions among the GDB
|
50 |
|
|
Maintainers. Of course, anyone - whether they hold a position but not the
|
51 |
|
|
relevant one for a particular patch, or are just following along on the
|
52 |
|
|
mailing lists for fun, or anything in between - may suggest changes or
|
53 |
|
|
ask questions about a patch!
|
54 |
|
|
|
55 |
|
|
There's also a couple of other people who play special roles in the GDB
|
56 |
|
|
community, separately from the patch process:
|
57 |
|
|
|
58 |
|
|
- The GDB Steering Committee.
|
59 |
|
|
|
60 |
|
|
These are the official (FSF-appointed) maintainers of GDB. They have
|
61 |
|
|
final and overriding authority for all GDB-related decisions, including
|
62 |
|
|
anything described in this file. The committee is not generally
|
63 |
|
|
involved in day-to-day development (although its members may be, as
|
64 |
|
|
individuals).
|
65 |
|
|
|
66 |
|
|
- The Release Manager.
|
67 |
|
|
|
68 |
|
|
This developer is in charge of making new releases of GDB.
|
69 |
|
|
|
70 |
|
|
- The Patch Champions.
|
71 |
|
|
|
72 |
|
|
These volunteers make sure that no contribution is overlooked or
|
73 |
|
|
forgotten.
|
74 |
|
|
|
75 |
|
|
Most changes to the list of maintainers in this file are handled by
|
76 |
|
|
consensus among the global maintainers and any other involved parties.
|
77 |
|
|
In cases where consensus can not be reached, the global maintainers may
|
78 |
|
|
ask the Steering Committee for a final decision.
|
79 |
|
|
|
80 |
|
|
|
81 |
|
|
The Obvious Fix Rule
|
82 |
|
|
--------------------
|
83 |
|
|
|
84 |
|
|
All maintainers listed in this file, including the Write After Approval
|
85 |
|
|
developers, are allowed to check in obvious fixes.
|
86 |
|
|
|
87 |
|
|
An "obvious fix" means that there is no possibility that anyone will
|
88 |
|
|
disagree with the change.
|
89 |
|
|
|
90 |
|
|
A good mental test is "will the person who hates my work the most be
|
91 |
|
|
able to find fault with the change" - if so, then it's not obvious and
|
92 |
|
|
needs to be posted first. :-)
|
93 |
|
|
|
94 |
|
|
Something like changing or bypassing an interface is _not_ an obvious
|
95 |
|
|
fix, since such a change without discussion will result in
|
96 |
|
|
instantaneous and loud complaints.
|
97 |
|
|
|
98 |
|
|
For documentation changes, about the only kind of fix that is obvious
|
99 |
|
|
is correction of a typo or bad English usage.
|
100 |
|
|
|
101 |
|
|
|
102 |
|
|
GDB Steering Committee
|
103 |
|
|
----------------------
|
104 |
|
|
|
105 |
|
|
The members of the GDB Steering Committee are the FSF-appointed
|
106 |
|
|
maintainers of the GDB project.
|
107 |
|
|
|
108 |
|
|
The Steering Committee has final authority for all GDB-related topics;
|
109 |
|
|
they may make whatever changes that they deem necessary, or that the FSF
|
110 |
|
|
requests. However, they are generally not involved in day-to-day
|
111 |
|
|
development.
|
112 |
|
|
|
113 |
|
|
The current members of the steering committee are listed below, in
|
114 |
|
|
alphabetical order. Their affiliations are provided for reference only -
|
115 |
|
|
their membership on the Steering Committee is individual and not through
|
116 |
|
|
their affiliation, and they act on behalf of the GNU project.
|
117 |
|
|
|
118 |
|
|
Jim Blandy (Mozilla)
|
119 |
|
|
Andrew Cagney (Red Hat)
|
120 |
|
|
Robert Dewar (AdaCore, NYU)
|
121 |
|
|
Klee Dienes (Apple)
|
122 |
|
|
Paul Hilfinger (UC Berkeley)
|
123 |
|
|
Dan Jacobowitz (CodeSourcery)
|
124 |
|
|
Stan Shebs (Mozilla)
|
125 |
|
|
Richard Stallman (FSF)
|
126 |
|
|
Ian Lance Taylor (C2)
|
127 |
|
|
Todd Whitesel
|
128 |
|
|
|
129 |
|
|
|
130 |
|
|
Global Maintainers
|
131 |
|
|
------------------
|
132 |
|
|
|
133 |
|
|
The global maintainers may review and commit any change to GDB, except in
|
134 |
|
|
areas with a Responsible Maintainer available. For major changes, or
|
135 |
|
|
changes to areas with other active developers, global maintainers are
|
136 |
|
|
strongly encouraged to post their own patches for feedback before
|
137 |
|
|
committing.
|
138 |
|
|
|
139 |
|
|
The global maintainers are responsible for reviewing patches to any area
|
140 |
|
|
for which no Responsible Maintainer is listed.
|
141 |
|
|
|
142 |
|
|
Global maintainers also have the authority to revert patches which should
|
143 |
|
|
not have been applied, e.g. patches which were not approved, controversial
|
144 |
|
|
patches committed under the Obvious Fix Rule, patches with important bugs
|
145 |
|
|
that can't be immediately fixed, or patches which go against an accepted and
|
146 |
|
|
documented roadmap for GDB development. Any global maintainer may request
|
147 |
|
|
the reversion of a patch. If no global maintainer, or responsible
|
148 |
|
|
maintainer in the affected areas, supports the patch (except for the
|
149 |
|
|
maintainer who originally committed it), then after 48 hours the maintainer
|
150 |
|
|
who called for the reversion may revert the patch.
|
151 |
|
|
|
152 |
|
|
No one may reapply a reverted patch without the agreement of the maintainer
|
153 |
|
|
who reverted it, or bringing the issue to the GDB Steering Committee for
|
154 |
|
|
discussion.
|
155 |
|
|
|
156 |
|
|
At the moment there are no documented roadmaps for GDB development; in the
|
157 |
|
|
future, if there are, a reference to the list will be included here.
|
158 |
|
|
|
159 |
|
|
The current global maintainers are (in alphabetical order):
|
160 |
|
|
|
161 |
|
|
Jim Blandy jimb@mozilla.com
|
162 |
|
|
Joel Brobecker brobecker@adacore.com
|
163 |
|
|
Kevin Buettner kevinb@redhat.com
|
164 |
|
|
Andrew Cagney cagney@gnu.org
|
165 |
|
|
Daniel Jacobowitz dan@debian.org
|
166 |
|
|
Mark Kettenis kettenis@gnu.org
|
167 |
|
|
Stan Shebs shebs@mozilla.com
|
168 |
|
|
Michael Snyder msnyder@specifix.com
|
169 |
|
|
Ulrich Weigand Ulrich.Weigand@de.ibm.com
|
170 |
|
|
Elena Zannoni ezannoni@redhat.com
|
171 |
|
|
Eli Zaretskii eliz@gnu.org
|
172 |
|
|
|
173 |
|
|
|
174 |
|
|
Release Manager
|
175 |
|
|
---------------
|
176 |
|
|
|
177 |
|
|
The current release manager is: Joel Brobecker
|
178 |
|
|
|
179 |
|
|
His responsibilities are:
|
180 |
|
|
|
181 |
|
|
* organizing, scheduling, and managing releases of GDB.
|
182 |
|
|
|
183 |
|
|
* deciding the approval and commit policies for release branches,
|
184 |
|
|
and can change them as needed.
|
185 |
|
|
|
186 |
|
|
|
187 |
|
|
|
188 |
|
|
Patch Champions
|
189 |
|
|
---------------
|
190 |
|
|
|
191 |
|
|
These volunteers track all patches submitted to the gdb-patches list. They
|
192 |
|
|
endeavor to prevent any posted patch from being overlooked; work with
|
193 |
|
|
contributors to meet GDB's coding style and general requirements, along with
|
194 |
|
|
FSF copyright assignments; remind (ping) responsible maintainers to review
|
195 |
|
|
patches; and ensure that contributors are given credit.
|
196 |
|
|
|
197 |
|
|
Current patch champions (in alphabetical order):
|
198 |
|
|
|
199 |
|
|
Randolph Chung
|
200 |
|
|
|
201 |
|
|
|
202 |
|
|
|
203 |
|
|
Responsible Maintainers
|
204 |
|
|
-----------------------
|
205 |
|
|
|
206 |
|
|
These developers have agreed to review patches in specific areas of GDB, in
|
207 |
|
|
which they have knowledge and experience. These areas are generally broad;
|
208 |
|
|
the role of a responsible maintainer is to provide coherent and cohesive
|
209 |
|
|
structure within their area of GDB, to assure that patches from many
|
210 |
|
|
different contributors all work together for the best results.
|
211 |
|
|
|
212 |
|
|
Global maintainers will defer to responsible maintainers within their areas,
|
213 |
|
|
as long as the responsible maintainer is active. Active means that
|
214 |
|
|
responsible maintainers agree to review submitted patches in their area
|
215 |
|
|
promptly; patches and followups should generally be answered within a week.
|
216 |
|
|
If a responsible maintainer is interested in reviewing a patch but will not
|
217 |
|
|
have time within a week of posting, the maintainer should send an
|
218 |
|
|
acknowledgement of the patch to the gdb-patches mailing list, and
|
219 |
|
|
plan to follow up with a review within a month. These deadlines are for
|
220 |
|
|
initial responses to a patch - if the maintainer has suggestions
|
221 |
|
|
or questions, it may take an extended discussion before the patch
|
222 |
|
|
is ready to commit. There are no written requirements for discussion,
|
223 |
|
|
but maintainers are asked to be responsive.
|
224 |
|
|
|
225 |
|
|
If a responsible maintainer misses these deadlines occasionally (e.g.
|
226 |
|
|
vacation or unexpected workload), it's not a disaster - any global
|
227 |
|
|
maintainer may step in to review the patch. But sometimes life intervenes
|
228 |
|
|
more permanently, and a maintainer may no longer have time for these duties.
|
229 |
|
|
When this happens, he or she should step down (either into the Authorized
|
230 |
|
|
Committers section if still interested in the area, or simply removed from
|
231 |
|
|
the list of Responsible Maintainers if not).
|
232 |
|
|
|
233 |
|
|
If a responsible maintainer is unresponsive for an extended period of time
|
234 |
|
|
without stepping down, please contact the Global Maintainers; they will try
|
235 |
|
|
to contact the maintainer directly and fix the problem - potentially by
|
236 |
|
|
removing that maintainer from their listed position.
|
237 |
|
|
|
238 |
|
|
If there are several maintainers for a given domain then any one of them
|
239 |
|
|
may review a submitted patch.
|
240 |
|
|
|
241 |
|
|
Target Instruction Set Architectures:
|
242 |
|
|
|
243 |
|
|
The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
|
244 |
|
|
(Operating System / Application Binary Interface) issues including CPU
|
245 |
|
|
variants.
|
246 |
|
|
|
247 |
|
|
The Target/Architecture maintainer works with the host maintainer when
|
248 |
|
|
resolving build issues. The Target/Architecture maintainer works with
|
249 |
|
|
the native maintainer when resolving ABI issues.
|
250 |
|
|
|
251 |
|
|
alpha --target=alpha-elf ,-Werror
|
252 |
|
|
|
253 |
|
|
arm --target=arm-elf ,-Werror
|
254 |
|
|
Richard Earnshaw rearnsha@arm.com
|
255 |
|
|
|
256 |
|
|
avr --target=avr ,-Werror
|
257 |
|
|
|
258 |
|
|
cris --target=cris-elf ,-Werror ,
|
259 |
|
|
(sim does not build with -Werror)
|
260 |
|
|
|
261 |
|
|
frv --target=frv-elf ,-Werror
|
262 |
|
|
|
263 |
|
|
h8300 --target=h8300-elf ,-Werror
|
264 |
|
|
|
265 |
|
|
i386 --target=i386-elf ,-Werror
|
266 |
|
|
Mark Kettenis kettenis@gnu.org
|
267 |
|
|
|
268 |
|
|
ia64 --target=ia64-linux-gnu ,-Werror
|
269 |
|
|
(--target=ia64-elf broken)
|
270 |
|
|
|
271 |
|
|
m32c --target=m32c-elf ,-Werror
|
272 |
|
|
Jim Blandy, jimb@codesourcery.com
|
273 |
|
|
|
274 |
|
|
m32r --target=m32r-elf ,-Werror
|
275 |
|
|
|
276 |
|
|
m68hc11 --target=m68hc11-elf ,-Werror ,
|
277 |
|
|
Stephane Carrez stcarrez@nerim.fr
|
278 |
|
|
|
279 |
|
|
m68k --target=m68k-elf ,-Werror
|
280 |
|
|
|
281 |
|
|
m88k --target=m88k-openbsd ,-Werror
|
282 |
|
|
Mark Kettenis kettenis@gnu.org
|
283 |
|
|
|
284 |
|
|
mcore Deleted
|
285 |
|
|
|
286 |
|
|
mep --target=mep-elf ,-Werror
|
287 |
|
|
Kevin Buettner kevinb@redhat.com
|
288 |
|
|
|
289 |
|
|
mips --target=mips-elf ,-Werror
|
290 |
|
|
|
291 |
|
|
mn10300 --target=mn10300-elf broken
|
292 |
|
|
(sim/ dies with make -j)
|
293 |
|
|
Michael Snyder msnyder@specifix.com
|
294 |
|
|
|
295 |
|
|
ms1 --target=ms1-elf ,-Werror
|
296 |
|
|
Kevin Buettner kevinb@redhat.com
|
297 |
|
|
|
298 |
|
|
ns32k Deleted
|
299 |
|
|
|
300 |
|
|
pa --target=hppa-elf ,-Werror
|
301 |
|
|
|
302 |
|
|
powerpc --target=powerpc-eabi ,-Werror
|
303 |
|
|
|
304 |
|
|
s390 --target=s390-linux-gnu ,-Werror
|
305 |
|
|
|
306 |
|
|
score --target=score-elf
|
307 |
|
|
Qinwei qinwei@sunnorth.com.cn
|
308 |
|
|
|
309 |
|
|
sh --target=sh-elf ,-Werror
|
310 |
|
|
--target=sh64-elf ,-Werror
|
311 |
|
|
|
312 |
|
|
sparc --target=sparc64-solaris2.10 ,-Werror
|
313 |
|
|
(--target=sparc-elf broken)
|
314 |
|
|
|
315 |
|
|
spu --target=spu-elf ,-Werror
|
316 |
|
|
Ulrich Weigand uweigand@de.ibm.com
|
317 |
|
|
|
318 |
|
|
v850 --target=v850-elf ,-Werror
|
319 |
|
|
|
320 |
|
|
vax --target=vax-netbsd ,-Werror
|
321 |
|
|
|
322 |
|
|
x86-64 --target=x86_64-linux-gnu ,-Werror
|
323 |
|
|
|
324 |
|
|
xstormy16 --target=xstormy16-elf
|
325 |
|
|
Corinna Vinschen vinschen@redhat.com
|
326 |
|
|
|
327 |
|
|
xtensa --target=xtensa-elf
|
328 |
|
|
Maxim Grigoriev maxim2405@gmail.com
|
329 |
|
|
|
330 |
|
|
All developers recognized by this file can make arbitrary changes to
|
331 |
|
|
OBSOLETE targets.
|
332 |
|
|
|
333 |
|
|
The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
|
334 |
|
|
above targets.
|
335 |
|
|
|
336 |
|
|
|
337 |
|
|
Host/Native:
|
338 |
|
|
|
339 |
|
|
The Native maintainer is responsible for target specific native
|
340 |
|
|
support - typically shared libraries and quirks to procfs/ptrace/...
|
341 |
|
|
The Native maintainer works with the Arch and Core maintainers when
|
342 |
|
|
resolving more generic problems.
|
343 |
|
|
|
344 |
|
|
The host maintainer ensures that gdb can be built as a cross debugger on
|
345 |
|
|
their platform.
|
346 |
|
|
|
347 |
|
|
AIX Joel Brobecker brobecker@adacore.com
|
348 |
|
|
|
349 |
|
|
djgpp native Eli Zaretskii eliz@gnu.org
|
350 |
|
|
GNU Hurd Alfred M. Szmidt ams@gnu.org
|
351 |
|
|
MS Windows (NT, '00, 9x, Me, XP) host & native
|
352 |
|
|
Chris Faylor cgf@alum.bu.edu
|
353 |
|
|
GNU/Linux/x86 native & host
|
354 |
|
|
Mark Kettenis kettenis@gnu.org
|
355 |
|
|
GNU/Linux MIPS native & host
|
356 |
|
|
Daniel Jacobowitz dan@debian.org
|
357 |
|
|
GNU/Linux m68k Andreas Schwab schwab@suse.de
|
358 |
|
|
FreeBSD native & host Mark Kettenis kettenis@gnu.org
|
359 |
|
|
|
360 |
|
|
|
361 |
|
|
|
362 |
|
|
Core: Generic components used by all of GDB
|
363 |
|
|
|
364 |
|
|
tracing Michael Snyder msnyder@specifix.com
|
365 |
|
|
threads Michael Snyder msnyder@specifix.com
|
366 |
|
|
Mark Kettenis kettenis@gnu.org
|
367 |
|
|
language support
|
368 |
|
|
Ada Joel Brobecker brobecker@adacore.com
|
369 |
|
|
Paul Hilfinger hilfinger@gnat.com
|
370 |
|
|
C++ Daniel Jacobowitz dan@debian.org
|
371 |
|
|
Objective C support Adam Fedor fedor@gnu.org
|
372 |
|
|
shared libs Kevin Buettner kevinb@redhat.com
|
373 |
|
|
MI interface Vladimir Prus vladimir@codesourcery.com
|
374 |
|
|
|
375 |
|
|
documentation Eli Zaretskii eliz@gnu.org
|
376 |
|
|
(including NEWS)
|
377 |
|
|
testsuite
|
378 |
|
|
gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
|
379 |
|
|
threads (gdb.threads) Michael Snyder msnyder@specifix.com
|
380 |
|
|
trace (gdb.trace) Michael Snyder msnyder@specifix.com
|
381 |
|
|
|
382 |
|
|
|
383 |
|
|
UI: External (user) interfaces.
|
384 |
|
|
|
385 |
|
|
gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
|
386 |
|
|
Keith Seitz keiths@redhat.com
|
387 |
|
|
libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
|
388 |
|
|
|
389 |
|
|
|
390 |
|
|
Misc:
|
391 |
|
|
|
392 |
|
|
gdb/gdbserver Daniel Jacobowitz dan@debian.org
|
393 |
|
|
|
394 |
|
|
Makefile.in, configure* ALL
|
395 |
|
|
|
396 |
|
|
mmalloc/ ALL Host maintainers
|
397 |
|
|
|
398 |
|
|
sim/ See sim/MAINTAINERS
|
399 |
|
|
|
400 |
|
|
readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
|
401 |
|
|
ALL
|
402 |
|
|
Host maintainers (host dependant parts)
|
403 |
|
|
(but get your changes into the master version)
|
404 |
|
|
|
405 |
|
|
tcl/ tk/ itcl/ ALL
|
406 |
|
|
|
407 |
|
|
|
408 |
|
|
Authorized Committers
|
409 |
|
|
---------------------
|
410 |
|
|
|
411 |
|
|
These are developers working on particular areas of GDB, who are trusted to
|
412 |
|
|
commit their own (or other developers') patches in those areas without
|
413 |
|
|
further review from a Global Maintainer or Responsible Maintainer. They are
|
414 |
|
|
under no obligation to review posted patches - but, of course, are invited
|
415 |
|
|
to do so!
|
416 |
|
|
|
417 |
|
|
PowerPC Andrew Cagney cagney@gnu.org
|
418 |
|
|
CRIS Hans-Peter Nilsson hp@bitrange.com
|
419 |
|
|
IA64 Jeff Johnston jjohnstn@redhat.com
|
420 |
|
|
MIPS Joel Brobecker brobecker@adacore.com
|
421 |
|
|
m32r Kei Sakamoto sakamoto.kei@renesas.com
|
422 |
|
|
PowerPC Kevin Buettner kevinb@redhat.com
|
423 |
|
|
CRIS Orjan Friberg orjanf@axis.com
|
424 |
|
|
HPPA Randolph Chung tausq@debian.org
|
425 |
|
|
S390 Ulrich Weigand uweigand@de.ibm.com
|
426 |
|
|
djgpp DJ Delorie dj@delorie.com
|
427 |
|
|
[Please use this address to contact DJ about DJGPP]
|
428 |
|
|
tui Stephane Carrez stcarrez@nerim.fr
|
429 |
|
|
ia64 Kevin Buettner kevinb@redhat.com
|
430 |
|
|
AIX Kevin Buettner kevinb@redhat.com
|
431 |
|
|
GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
|
432 |
|
|
gdb.java tests Anthony Green green@redhat.com
|
433 |
|
|
FreeBSD native & host David O'Brien obrien@freebsd.org
|
434 |
|
|
event loop Elena Zannoni ezannoni@redhat.com
|
435 |
|
|
generic symtabs Elena Zannoni ezannoni@redhat.com
|
436 |
|
|
dwarf readers Elena Zannoni ezannoni@redhat.com
|
437 |
|
|
elf reader Elena Zannoni ezannoni@redhat.com
|
438 |
|
|
stabs reader Elena Zannoni ezannoni@redhat.com
|
439 |
|
|
readline/ Elena Zannoni ezannoni@redhat.com
|
440 |
|
|
NetBSD native & host Jason Thorpe thorpej@netbsd.org
|
441 |
|
|
Pascal support Pierre Muller muller@sources.redhat.com
|
442 |
|
|
avr Theodore A. Roth troth@openavr.org
|
443 |
|
|
Modula-2 support Gaius Mulley gaius@glam.ac.uk
|
444 |
|
|
|
445 |
|
|
|
446 |
|
|
Write After Approval
|
447 |
|
|
(alphabetic)
|
448 |
|
|
|
449 |
|
|
To get recommended for the Write After Approval list you need a valid
|
450 |
|
|
FSF assignment and have submitted one good patch.
|
451 |
|
|
|
452 |
|
|
Pedro Alves pedro_alves@portugalmail.pt
|
453 |
|
|
David Anderson davea@sgi.com
|
454 |
|
|
John David Anglin dave.anglin@nrc-cnrc.gc.ca
|
455 |
|
|
Shrinivas Atre shrinivasa@kpitcummins.com
|
456 |
|
|
Scott Bambrough scottb@netwinder.org
|
457 |
|
|
Thiago Jung Bauermann bauerman@br.ibm.com
|
458 |
|
|
Jan Beulich jbeulich@novell.com
|
459 |
|
|
Jim Blandy jimb@codesourcery.com
|
460 |
|
|
Philip Blundell philb@gnu.org
|
461 |
|
|
Per Bothner per@bothner.com
|
462 |
|
|
Joel Brobecker brobecker@adacore.com
|
463 |
|
|
Dave Brolley brolley@redhat.com
|
464 |
|
|
Paul Brook paul@codesourcery.com
|
465 |
|
|
Julian Brown julian@codesourcery.com
|
466 |
|
|
Kevin Buettner kevinb@redhat.com
|
467 |
|
|
Andrew Cagney cagney@gnu.org
|
468 |
|
|
David Carlton carlton@bactrian.org
|
469 |
|
|
Stephane Carrez stcarrez@nerim.fr
|
470 |
|
|
Michael Chastain mec.gnu@mindspring.com
|
471 |
|
|
Eric Christopher echristo@apple.com
|
472 |
|
|
Randolph Chung tausq@debian.org
|
473 |
|
|
Nick Clifton nickc@redhat.com
|
474 |
|
|
J.T. Conklin jtc@acorntoolworks.com
|
475 |
|
|
Brendan Conoboy blc@redhat.com
|
476 |
|
|
Ludovic Courtès ludo@gnu.org
|
477 |
|
|
DJ Delorie dj@redhat.com
|
478 |
|
|
Philippe De Muyter phdm@macqel.be
|
479 |
|
|
Dhananjay Deshpande dhananjayd@kpitcummins.com
|
480 |
|
|
Markus Deuling deuling@de.ibm.com
|
481 |
|
|
Klee Dienes kdienes@apple.com
|
482 |
|
|
Gabriel Dos Reis gdr@integrable-solutions.net
|
483 |
|
|
Richard Earnshaw rearnsha@arm.com
|
484 |
|
|
Steve Ellcey sje@cup.hp.com
|
485 |
|
|
Frank Ch. Eigler fche@redhat.com
|
486 |
|
|
Ben Elliston bje@gnu.org
|
487 |
|
|
Doug Evans dje@google.com
|
488 |
|
|
Adam Fedor fedor@gnu.org
|
489 |
|
|
Brian Ford ford@vss.fsi.com
|
490 |
|
|
Orjan Friberg orjanf@axis.com
|
491 |
|
|
Nathan Froyd froydnj@codesourcery.com
|
492 |
|
|
Gary Funck gary@intrepid.com
|
493 |
|
|
Paul Gilliam pgilliam@us.ibm.com
|
494 |
|
|
Raoul Gough RaoulGough@yahoo.co.uk
|
495 |
|
|
Anthony Green green@redhat.com
|
496 |
|
|
Matthew Green mrg@eterna.com.au
|
497 |
|
|
Maxim Grigoriev maxim2405@gmail.com
|
498 |
|
|
Jerome Guitton guitton@act-europe.fr
|
499 |
|
|
Ben Harris bjh21@netbsd.org
|
500 |
|
|
Richard Henderson rth@redhat.com
|
501 |
|
|
Aldy Hernandez aldyh@redhat.com
|
502 |
|
|
Paul Hilfinger hilfinger@gnat.com
|
503 |
|
|
Matt Hiller hiller@redhat.com
|
504 |
|
|
Kazu Hirata kazu@cs.umass.edu
|
505 |
|
|
Jeff Holcomb jeffh@redhat.com
|
506 |
|
|
Don Howard dhoward@redhat.com
|
507 |
|
|
Nick Hudson nick.hudson@dsl.pipex.com
|
508 |
|
|
Martin Hunt hunt@redhat.com
|
509 |
|
|
Jim Ingham jingham@apple.com
|
510 |
|
|
Baurzhan Ismagulov ibr@radix50.net
|
511 |
|
|
Manoj Iyer manjo@austin.ibm.com
|
512 |
|
|
Daniel Jacobowitz dan@debian.org
|
513 |
|
|
Andreas Jaeger aj@suse.de
|
514 |
|
|
Jeff Johnston jjohnstn@redhat.com
|
515 |
|
|
Geoff Keating geoffk@redhat.com
|
516 |
|
|
Mark Kettenis kettenis@gnu.org
|
517 |
|
|
Jim Kingdon kingdon@panix.com
|
518 |
|
|
Jan Kratochvil jan.kratochvil@redhat.com
|
519 |
|
|
Jonathan Larmour jlarmour@redhat.co.uk
|
520 |
|
|
Jeff Law law@redhat.com
|
521 |
|
|
David Lecomber david@streamline-computing.com
|
522 |
|
|
Robert Lipe rjl@sco.com
|
523 |
|
|
H.J. Lu hjl.tools@gmail.com
|
524 |
|
|
Michal Ludvig mludvig@suse.cz
|
525 |
|
|
Luis Machado luisgpm@br.ibm.com
|
526 |
|
|
Glen McCready gkm@redhat.com
|
527 |
|
|
Greg McGary greg@mcgary.org
|
528 |
|
|
Roland McGrath roland@redhat.com
|
529 |
|
|
Bryce McKinlay mckinlay@redhat.com
|
530 |
|
|
Jason Merrill jason@redhat.com
|
531 |
|
|
David S. Miller davem@redhat.com
|
532 |
|
|
Mark Mitchell mark@codesourcery.com
|
533 |
|
|
Marko Mlinar markom@opencores.org
|
534 |
|
|
Alan Modra amodra@bigpond.net.au
|
535 |
|
|
Jason Molenda jmolenda@apple.com
|
536 |
|
|
Pierre Muller muller@sources.redhat.com
|
537 |
|
|
Gaius Mulley gaius@glam.ac.uk
|
538 |
|
|
Joseph Myers joseph@codesourcery.com
|
539 |
|
|
Fernando Nasser fnasser@redhat.com
|
540 |
|
|
Adam Nemet anemet@caviumnetworks.com
|
541 |
|
|
Nathanael Nerode neroden@gcc.gnu.org
|
542 |
|
|
Hans-Peter Nilsson hp@bitrange.com
|
543 |
|
|
David O'Brien obrien@freebsd.org
|
544 |
|
|
Alexandre Oliva aoliva@redhat.com
|
545 |
|
|
Denis Pilat denis.pilat@st.com
|
546 |
|
|
Vladimir Prus vladimir@codesourcery.com
|
547 |
|
|
Qinwei qinwei@sunnorth.com.cn
|
548 |
|
|
Ramana Radhakrishnan ramana.radhakrishnan@codito.com
|
549 |
|
|
Frederic Riss frederic.riss@st.com
|
550 |
|
|
Tom Rix trix@redhat.com
|
551 |
|
|
Nick Roberts nickrob@snap.net.nz
|
552 |
|
|
Bob Rossi bob_rossi@cox.net
|
553 |
|
|
Theodore A. Roth troth@openavr.org
|
554 |
|
|
Ian Roxborough irox@redhat.com
|
555 |
|
|
Maciej W. Rozycki macro@linux-mips.org
|
556 |
|
|
Grace Sainsbury graces@redhat.com
|
557 |
|
|
Kei Sakamoto sakamoto.kei@renesas.com
|
558 |
|
|
Mark Salter msalter@redhat.com
|
559 |
|
|
Richard Sandiford richard@codesourcery.com
|
560 |
|
|
Peter Schauer Peter.Schauer@mytum.de
|
561 |
|
|
Andreas Schwab schwab@suse.de
|
562 |
|
|
Keith Seitz keiths@redhat.com
|
563 |
|
|
Carlos Eduardo Seo cseo@linux.vnet.ibm.com
|
564 |
|
|
Stan Shebs shebs@mozilla.com
|
565 |
|
|
Mark Shinwell shinwell@codesourcery.com
|
566 |
|
|
Aidan Skinner aidan@velvet.net
|
567 |
|
|
Jiri Smid smid@suse.cz
|
568 |
|
|
David Smith dsmith@redhat.com
|
569 |
|
|
Stephen P. Smith ischis2@cox.net
|
570 |
|
|
Jackie Smith Cashion jsmith@redhat.com
|
571 |
|
|
Michael Snyder msnyder@specifix.com
|
572 |
|
|
Petr Sorfa petrs@caldera.com
|
573 |
|
|
Andrew Stubbs andrew.stubbs@st.com
|
574 |
|
|
Ian Lance Taylor ian@airs.com
|
575 |
|
|
Gary Thomas gthomas@redhat.com
|
576 |
|
|
Jason Thorpe thorpej@netbsd.org
|
577 |
|
|
Caroline Tice ctice@apple.com
|
578 |
|
|
Tom Tromey tromey@redhat.com
|
579 |
|
|
David Ung davidu@mips.com
|
580 |
|
|
D Venkatasubramanian dvenkat@noida.hcltech.com
|
581 |
|
|
Corinna Vinschen vinschen@redhat.com
|
582 |
|
|
Keith Walker keith.walker@arm.com
|
583 |
|
|
Kris Warkentin kewarken@qnx.com
|
584 |
|
|
Ulrich Weigand uweigand@de.ibm.com
|
585 |
|
|
Nathan Williams nathanw@wasabisystems.com
|
586 |
|
|
Bob Wilson bob.wilson@acm.org
|
587 |
|
|
Jim Wilson wilson@specifix.com
|
588 |
|
|
Elena Zannoni ezannoni@redhat.com
|
589 |
|
|
Eli Zaretskii eliz@gnu.org
|
590 |
|
|
Wu Zhou woodzltc@cn.ibm.com
|
591 |
|
|
Yoshinori Sato ysato@users.sourceforge.jp
|
592 |
|
|
|
593 |
|
|
|
594 |
|
|
Past Maintainers
|
595 |
|
|
|
596 |
|
|
Whenever removing yourself, or someone else, from this file, consider
|
597 |
|
|
listing their areas of development here for posterity.
|
598 |
|
|
|
599 |
|
|
Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
|
600 |
|
|
Jeff Law (hppa) law at cygnus dot com
|
601 |
|
|
Daniel Berlin (C++ support) dan at cgsoftware dot com
|
602 |
|
|
Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
|
603 |
|
|
David Taylor (d10v, sparc, utils, defs,
|
604 |
|
|
expression evaluator, language support) taylor at candd dot org
|
605 |
|
|
J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
|
606 |
|
|
Frank Ch. Eigler (sim) fche at redhat dot com
|
607 |
|
|
Per Bothner (Java) per at bothner dot com
|
608 |
|
|
Anthony Green (Java) green at redhat dot com
|
609 |
|
|
Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
|
610 |
|
|
Mark Salter (testsuite/lib+config) msalter at redhat dot com
|
611 |
|
|
Jim Kingdon (web pages) kingdon at panix dot com
|
612 |
|
|
Jim Ingham (gdbtk, libgui) jingham at apple dot com
|
613 |
|
|
Mark Kettenis (hurd native) kettenis at gnu dot org
|
614 |
|
|
Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
|
615 |
|
|
Robert Lipe (SCO/Unixware) rjl at sco dot com
|
616 |
|
|
Peter Schauer (global, AIX, xcoffsolib,
|
617 |
|
|
Solaris/x86) Peter.Schauer at mytum dot de
|
618 |
|
|
Scott Bambrough (ARM) scottb at netwinder dot org
|
619 |
|
|
Philippe De Muyter (coff) phdm at macqel dot be
|
620 |
|
|
Michael Chastain (testsuite) mec.gnu at mindspring dot com
|
621 |
|
|
Fred Fish (global)
|
622 |
|
|
|
623 |
|
|
|
624 |
|
|
|
625 |
|
|
Folks that have been caught up in a paper trail:
|
626 |
|
|
|
627 |
|
|
David Carlton carlton@bactrian.org
|
628 |
|
|
|
629 |
|
|
;; Local Variables:
|
630 |
|
|
;; coding: utf-8
|
631 |
|
|
;; End:
|