* m32c-asm.c: Regenerate.
[deliverable/binutils-gdb.git] / gdb / MAINTAINERS
CommitLineData
e990a46e 1 GDB Maintainers
b2a74f99
DJ
2 ===============
3
4
5 Overview
6 --------
7
8This file describes different groups of people who are, together, the
9maintainers and developers of the GDB project. Don't worry - it sounds
10more complicated than it really is.
11
12There are four groups of GDB developers, covering the patch development and
13review 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
40All maintainers are encouraged to post major patches to the gdb-patches
41mailing list for comments, even if they have the authority to commit the
42patch without review from another maintainer. This especially includes
43patches which change internal interfaces (e.g. global functions, data
44structures) or external interfaces (e.g. user, remote, MI, et cetera).
45
46The term "review" is used in this file to describe several kinds of feedback
47from a maintainer: approval, rejection, and requests for changes or
48clarification with the intention of approving a revised version. Review is
49a privilege and/or responsibility of various positions among the GDB
50Maintainers. Of course, anyone - whether they hold a position but not the
51relevant one for a particular patch, or are just following along on the
52mailing lists for fun, or anything in between - may suggest changes or
53ask questions about a patch!
54
55There's also a couple of other people who play special roles in the GDB
56community, 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
75Most changes to the list of maintainers in this file are handled by
76consensus among the global maintainers and any other involved parties.
77In cases where consensus can not be reached, the global maintainers may
78ask the Steering Committee for a final decision.
79
80
81 The Obvious Fix Rule
82 --------------------
83
84All maintainers listed in this file, including the Write After Approval
85developers, are allowed to check in obvious fixes.
86
87An "obvious fix" means that there is no possibility that anyone will
88disagree with the change.
89
90A good mental test is "will the person who hates my work the most be
91able to find fault with the change" - if so, then it's not obvious and
92needs to be posted first. :-)
93
94Something like changing or bypassing an interface is _not_ an obvious
95fix, since such a change without discussion will result in
96instantaneous and loud complaints.
97
e990a46e
AC
98
99 GDB Steering Committee
b2a74f99 100 ----------------------
e990a46e
AC
101
102The members of the GDB Steering Committee are the FSF-appointed
103maintainers of the GDB project.
104
b2a74f99
DJ
105The Steering Committee has final authority for all GDB-related topics;
106they may make whatever changes that they deem necessary, or that the FSF
107requests. However, they are generally not involved in day-to-day
108development.
109
110The current members of the steering committee are listed below, in
111alphabetical order. Their affiliations are provided for reference only -
112their membership on the Steering Committee is individual and not through
113their affiliation, and they act on behalf of the GNU project.
114
e990a46e
AC
115 Jim Blandy (Red Hat)
116 Andrew Cagney (Red Hat)
117 Robert Dewar (AdaCore, NYU)
118 Klee Dienes (Apple)
119 Paul Hilfinger (UC Berkeley)
120 Dan Jacobowitz (CodeSourcery)
121 Stan Shebs (Apple)
122 Richard Stallman (FSF)
123 Ian Lance Taylor (C2)
124 Todd Whitesel
ef7b4488 125
5185fdd7 126
b2a74f99
DJ
127 Global Maintainers
128 ------------------
129
130The global maintainers may review and commit any change to GDB, except in
131areas with a Responsible Maintainer available. For major changes, or
132changes to areas with other active developers, global maintainers are
133strongly encouraged to post their own patches for feedback before
134committing.
135
136The global maintainers are responsible for reviewing patches to any area
137for which no Responsible Maintainer is listed.
138
139Global maintainers also have the authority to revert patches which should
140not have been applied, e.g. patches which were not approved, controversial
141patches committed under the Obvious Fix Rule, patches with important bugs
142that can't be immediately fixed, or patches which go against an accepted and
143documented roadmap for GDB development. Any global maintainer may request
144the reversion of a patch. If no global maintainer, or responsible
145maintainer in the affected areas, supports the patch (except for the
146maintainer who originally committed it), then after 48 hours the maintainer
147who called for the reversion may revert the patch.
148
149No one may reapply a reverted patch without the agreement of the maintainer
150who reverted it, or bringing the issue to the GDB Steering Committee for
151discussion.
152
153At the moment there are no documented roadmaps for GDB development; in the
154future, if there are, a reference to the list will be included here.
155
156The current global maintainers are (in alphabetical order):
5185fdd7 157
f408839d 158Jim Blandy jimb@red-bean.com
904507ce 159Kevin Buettner kevinb@redhat.com
1db2a798 160Andrew Cagney cagney@gnu.org
abdcb2a5 161Fred Fish fnf@ninemoons.com
0ec30a36 162Daniel Jacobowitz dan@debian.org
1b57acd2 163Mark Kettenis kettenis@gnu.org
e7411eaa 164Stan Shebs shebs@apple.com
f9e2d830 165Michael Snyder msnyder@redhat.com
904507ce
AC
166Elena Zannoni ezannoni@redhat.com
167Eli Zaretskii eliz@gnu.org
5185fdd7 168
f5bca8e7 169
b2a74f99
DJ
170 Release Manager
171 ---------------
5185fdd7 172
b2a74f99 173The current release manager is: Joel Brobecker <brobecker@adacore.com>
5185fdd7 174
b2a74f99 175His responsibilities are:
36c2118f 176
b2a74f99 177 * organizing, scheduling, and managing releases of GDB.
538aae9d 178
b2a74f99
DJ
179 * deciding the approval and commit policies for release branches,
180 and can change them as needed.
5185fdd7 181
58cfabe6 182
58cfabe6 183
b2a74f99
DJ
184 Patch Champions
185 ---------------
58cfabe6 186
b2a74f99
DJ
187These volunteers track all patches submitted to the gdb-patches list. They
188endeavor to prevent any posted patch from being overlooked; work with
189contributors to meet GDB's coding style and general requirements, along with
190FSF copyright assignments; remind (ping) responsible maintainers to review
191patches; and ensure that contributors are given credit.
58cfabe6 192
b2a74f99 193Current patch champions (in alphabetical order):
54c92070 194
b2a74f99 195 Daniel Jacobowitz <dan@debian.org>
58cfabe6 196
a60a53c5 197
a60a53c5 198
b2a74f99
DJ
199 Responsible Maintainers
200 -----------------------
201
202These developers have agreed to review patches in specific areas of GDB, in
203which they have knowledge and experience. These areas are generally broad;
204the role of a responsible maintainer is to provide coherent and cohesive
205structure within their area of GDB, to assure that patches from many
206different contributors all work together for the best results.
a60a53c5 207
b2a74f99
DJ
208Global maintainers will defer to responsible maintainers within their areas,
209as long as the responsible maintainer is active. Active means that
210responsible maintainers agree to review submitted patches in their area
211promptly; patches and followups should generally be answered within a week.
212If a responsible maintainer is interested in reviewing a patch but will not
213have time within a week of posting, the maintainer should send an
214acknowledgement of the patch to the gdb-patches mailing list, and
215plan to follow up with a review within a month. These deadlines are for
216initial responses to a patch - if the maintainer has suggestions
217or questions, it may take an extended discussion before the patch
218is ready to commit. There are no written requirements for discussion,
219but maintainers are asked to be responsive.
220
221If a responsible maintainer misses these deadlines occasionally (e.g.
222vacation or unexpected workload), it's not a disaster - any global
223maintainer may step in to review the patch. But sometimes life intervenes
224more permanently, and a maintainer may no longer have time for these duties.
225When this happens, he or she should step down (either into the Authorized
226Committers section if still interested in the area, or simply removed from
227the list of Responsible Maintainers if not).
228
229If a responsible maintainer is unresponsive for an extended period of time
230without stepping down, please contact the Global Maintainers; they will try
231to contact the maintainer directly and fix the problem - potentially by
232removing that maintainer from their listed position.
233
234If there are several maintainers for a given domain then any one of them
235may review a submitted patch.
a60a53c5 236
c1bab85b 237Target Instruction Set Architectures:
8860ff2e 238
91a533d4
AC
239The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
240(Operating System / Application Binary Interface) issues including CPU
241variants.
242
243The Target/Architecture maintainer works with the host maintainer when
244resolving build issues. The Target/Architecture maintainer works with
245the native maintainer when resolving ABI issues.
5185fdd7 246
8f9cbe01 247 alpha --target=alpha-elf ,-Werror
21a6f6bb 248
66140c26 249 arm --target=arm-elf ,-Werror
26806ce2 250 Richard Earnshaw rearnsha@arm.com
9b82661c 251
e33ce519 252 avr --target=avr ,-Werror
e33ce519 253
4a72630a 254 cris --target=cris-elf ,-Werror
93755ae6 255
61c82a3b 256 d10v OBSOLETE
21a6f6bb 257
53e8aaea 258 frv --target=frv-elf ,-Werror
53e8aaea 259
87d088f5 260 h8300 --target=h8300-elf ,-Werror
9b82661c 261
c1bab85b 262 i386 --target=i386-elf ,-Werror
21a6f6bb
AC
263 Mark Kettenis kettenis@gnu.org
264
32089c7c
AC
265 ia64 --target=ia64-linux-gnu ,-Werror
266 (--target=ia64-elf broken)
9b82661c 267
9644bbdd 268 m32r --target=m32r-elf ,-Werror
9b82661c 269
53fe9346 270 m68hc11 --target=m68hc11-elf ,-Werror ,
2be99286 271 Stephane Carrez stcarrez@nerim.fr
9b82661c 272
043c9cdc 273 m68k --target=m68k-elf ,-Werror
9b82661c 274
1698f4e7
MK
275 m88k --target=m88k-openbsd ,-Werror
276 Mark Kettenis kettenis@gnu.org
9b82661c 277
9445aa30 278 mcore Deleted
9b82661c 279
c1bab85b 280 mips --target=mips-elf ,-Werror
9b82661c 281
87d088f5
AC
282 mn10300 --target=mn10300-elf broken
283 (sim/ dies with make -j)
5260ca71 284 Michael Snyder msnyder@redhat.com
9b82661c 285
37ebea84
KB
286 ms1 --target=ms1-elf ,-Werror
287 Kevin Buettner kevinb@redhat.com
288
9445aa30 289 ns32k Deleted
9b82661c 290
93449403 291 pa --target=hppa-elf ,-Werror
21a6f6bb 292
8dacb7ef 293 powerpc --target=powerpc-eabi ,-Werror
9b82661c 294
9f9d12b3 295 s390 --target=s390-linux-gnu ,-Werror
5769d3cd 296
5dbc6baa 297 sh --target=sh-elf ,-Werror
079c8cd0 298 --target=sh64-elf ,-Werror
9b82661c 299
043c9cdc 300 sparc --target=sparc-elf ,-Werror
9b82661c 301
181124bc 302 v850 --target=v850-elf ,-Werror
21a6f6bb 303
043c9cdc 304 vax --target=vax-netbsd ,-Werror
21a6f6bb 305
53fe9346 306 x86-64 --target=x86_64-linux-gnu ,-Werror
e4621584 307
b6fcb393 308 xstormy16 --target=xstormy16-elf
7c0a2a0a
CV
309 Corinna Vinschen vinschen@redhat.com
310
fcc87af1
AC
311All developers recognized by this file can make arbitrary changes to
312OBSOLETE targets.
9b82661c 313
684e56bf
AC
314The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
315above targets.
5185fdd7
AC
316
317
8860ff2e
AC
318Host/Native:
319
9b82661c
AC
320The Native maintainer is responsible for target specific native
321support - typically shared libraries and quirks to procfs/ptrace/...
322The Native maintainer works with the Arch and Core maintainers when
323resolving more generic problems.
8860ff2e 324
9175c9a3
MC
325The host maintainer ensures that gdb can be built as a cross debugger on
326their platform.
5185fdd7 327
f4d408c6 328AIX Joel Brobecker brobecker@adacore.com
e306c308 329
56a5d675 330djgpp native Eli Zaretskii eliz@gnu.org
842330b4 331MS Windows (NT, '00, 9x, Me, XP) host & native
859a326d 332 Chris Faylor cgf@alum.bu.edu
ef7b4488 333GNU/Linux/x86 native & host
ef7b4488 334 Mark Kettenis kettenis@gnu.org
6c8e04b5
DJ
335GNU/Linux MIPS native & host
336 Daniel Jacobowitz dan@debian.org
26806ce2 337GNU/Linux m68k Andreas Schwab schwab@suse.de
e255d535 338FreeBSD native & host Mark Kettenis kettenis@gnu.org
5185fdd7 339
9b82661c
AC
340
341
5185fdd7
AC
342Core: Generic components used by all of GDB
343
f9e2d830
AC
344tracing Michael Snyder msnyder@redhat.com
345threads Michael Snyder msnyder@redhat.com
a8596edf 346 Mark Kettenis kettenis@gnu.org
f4d408c6 347language support
8de3c354 348 C++ Daniel Jacobowitz dan@debian.org
3771659b 349 Objective C support Adam Fedor fedor@gnu.org
f4d408c6 350shared libs Kevin Buettner kevinb@redhat.com
e306c308 351
e8be95ae 352documentation Eli Zaretskii eliz@gnu.org
f4d408c6 353testsuite
5a703563 354 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
5a703563
FN
355 threads (gdb.threads) Michael Snyder msnyder@redhat.com
356 trace (gdb.trace) Michael Snyder msnyder@redhat.com
5185fdd7
AC
357
358
359UI: External (user) interfaces.
360
f4d408c6 361gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
54403c59 362 Keith Seitz keiths@redhat.com
f4d408c6 363libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
f5bca8e7
AC
364
365
366Misc:
367
3f289e6f
AC
368gdb/gdbserver Daniel Jacobowitz dan@debian.org
369
f5bca8e7 370Makefile.in, configure* ALL
7158fd7f
AC
371
372mmalloc/ ALL Host maintainers
373
519b2366
DJ
374NEWS ALL
375
f779ca99 376sim/ See sim/MAINTAINERS
5185fdd7 377
9ec7faef 378readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
f4d408c6 379 ALL
9ec7faef
AC
380 Host maintainers (host dependant parts)
381 (but get your changes into the master version)
382
f4d408c6 383tcl/ tk/ itcl/ ALL
ef7b4488 384
b2a74f99
DJ
385
386 Authorized Committers
387 ---------------------
388
389These are developers working on particular areas of GDB, who are trusted to
390commit their own (or other developers') patches in those areas without
391further review from a Global Maintainer or Responsible Maintainer. They are
392under no obligation to review posted patches - but, of course, are invited
393to do so!
394
f4d408c6
DJ
395PowerPC Andrew Cagney cagney@gnu.org
396CRIS Hans-Peter Nilsson hp@bitrange.com
397IA64 Jeff Johnston jjohnstn@redhat.com
398MIPS Joel Brobecker brobecker@adacore.com
399m32r Kei Sakamoto sakamoto.kei@renesas.com
400PowerPC Kevin Buettner kevinb@redhat.com
401CRIS Orjan Friberg orjanf@axis.com
402HPPA Randolph Chung tausq@debian.org
403S390 Ulrich Weigand uweigand@de.ibm.com
404djgpp DJ Delorie dj@delorie.com
405 [Please use this address to contact DJ about DJGPP]
406tui Stephane Carrez stcarrez@nerim.fr
407ia64 Kevin Buettner kevinb@redhat.com
408AIX Kevin Buettner kevinb@redhat.com
409GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
410gdb.java tests Anthony Green green@redhat.com
411FreeBSD native & host David O'Brien obrien@freebsd.org
412event loop Elena Zannoni ezannoni@redhat.com
413generic symtabs Elena Zannoni ezannoni@redhat.com
414dwarf readers Elena Zannoni ezannoni@redhat.com
415elf reader Elena Zannoni ezannoni@redhat.com
416stabs reader Elena Zannoni ezannoni@redhat.com
417readline/ Elena Zannoni ezannoni@redhat.com
418Kernel Object Display Fernando Nasser fnasser@redhat.com
419NetBSD native & host Jason Thorpe thorpej@netbsd.org
420Pascal support Pierre Muller muller@sources.redhat.com
421avr Theodore A. Roth troth@openavr.org
b2a74f99
DJ
422
423
e7745bde
AC
424 Write After Approval
425 (alphabetic)
5185fdd7 426
b76a2a57
AC
427To get recommended for the Write After Approval list you need a valid
428FSF assignment and have submitted one good patch.
429
b302179c 430David Anderson davea@sgi.com
871cce51 431John David Anglin dave.anglin@nrc-cnrc.gc.ca
062103ba 432Shrinivas Atre shrinivasa@kpitcummins.com
627054c8 433Scott Bambrough scottb@netwinder.org
ae2a31bf 434Jan Beulich jbeulich@novell.com
f408839d 435Jim Blandy jimb@red-bean.com
e7745bde 436Philip Blundell philb@gnu.org
627054c8 437Per Bothner per@bothner.com
1581f359 438Joel Brobecker brobecker@adacore.com
cdd463f9 439Dave Brolley brolley@redhat.com
dbf5be1c 440Paul Brook paul@codesourcery.com
627054c8 441Kevin Buettner kevinb@redhat.com
1db2a798 442Andrew Cagney cagney@gnu.org
58e23df4 443David Carlton carlton@bactrian.org
627054c8 444Stephane Carrez stcarrez@nerim.fr
68e39e73 445Michael Chastain mec.gnu@mindspring.com
e04e8f8a 446Eric Christopher echristo@apple.com
700c15aa 447Randolph Chung tausq@debian.org
f9e2d830 448Nick Clifton nickc@redhat.com
f4d408c6 449J.T. Conklin jtc@acorntoolworks.com
56296155 450Brendan Conoboy blc@redhat.com
eb944380 451DJ Delorie dj@redhat.com
eb944380 452Philippe De Muyter phdm@macqel.be
8bfdb672 453Dhananjay Deshpande dhananjayd@kpitcummins.com
6a41ff59 454Klee Dienes kdienes@apple.com
dd96c05b 455Richard Earnshaw rearnsha@arm.com
3ad97651 456Steve Ellcey sje@cup.hp.com
627054c8 457Frank Ch. Eigler fche@redhat.com
523f6a27 458Ben Elliston bje@gnu.org
e92f3704
JG
459Adam Fedor fedor@gnu.org
460Fred Fish fnf@ninemoons.com
283f90a7 461Brian Ford ford@vss.fsi.com
e92f3704 462Orjan Friberg orjanf@axis.com
386d4518 463Paul Gilliam pgilliam@us.ibm.com
cb123844 464Raoul Gough RaoulGough@yahoo.co.uk
627054c8 465Anthony Green green@redhat.com
181c3369 466Matthew Green mrg@eterna.com.au
a4ab2b5d 467Jerome Guitton guitton@act-europe.fr
1005d5ef 468Ben Harris bjh21@netbsd.org
23b95bcb 469Richard Henderson rth@redhat.com
814b3ba0 470Aldy Hernandez aldyh@redhat.com
e7745bde
AC
471Paul Hilfinger hilfinger@gnat.com
472Matt Hiller hiller@redhat.com
ed42d87b 473Kazu Hirata kazu@cs.umass.edu
e7745bde
AC
474Jeff Holcomb jeffh@redhat.com
475Don Howard dhoward@redhat.com
476Martin Hunt hunt@redhat.com
6a41ff59 477Jim Ingham jingham@apple.com
a80493b8 478Baurzhan Ismagulov ibr@radix50.net
7d97d5e2 479Manoj Iyer manjo@austin.ibm.com
2740bf6c 480Daniel Jacobowitz dan@debian.org
37965979 481Andreas Jaeger aj@suse.de
7e3cec17 482Jeff Johnston jjohnstn@redhat.com
e7745bde 483Geoff Keating geoffk@redhat.com
627054c8 484Mark Kettenis kettenis@gnu.org
f4d408c6 485Jim Kingdon kingdon@panix.com
f09cffe3 486Jonathan Larmour jlarmour@redhat.co.uk
eb944380 487Jeff Law law@redhat.com
b1bd302e 488David Lecomber david@streamline-computing.com
627054c8 489Robert Lipe rjl@sco.com
e7745bde 490H.J. Lu hjl@lucon.org
627054c8 491Michal Ludvig mludvig@suse.cz
f9e2d830 492Glen McCready gkm@redhat.com
ac2e0304 493Greg McGary greg@mcgary.org
a8cbc6f7 494Roland McGrath roland@redhat.com
723e0e3d 495Bryce McKinlay mckinlay@redhat.com
39c22d1a 496Jason Merrill jason@redhat.com
627054c8 497David S. Miller davem@redhat.com
89a72f9c 498Mark Mitchell mark@codesourcery.com
da615bee 499Marko Mlinar markom@opencores.org
ecd1107e 500Alan Modra amodra@bigpond.net.au
6d6b80e5 501Jason Molenda jmolenda@apple.com
47b95330 502Pierre Muller muller@sources.redhat.com
3d38a0a5 503Joseph Myers joseph@codesourcery.com
627054c8 504Fernando Nasser fnasser@redhat.com
d0f853e1 505Nathanael Nerode neroden@gcc.gnu.org
6eecb1c8 506Hans-Peter Nilsson hp@bitrange.com
627054c8 507David O'Brien obrien@freebsd.org
2748f097 508Alexandre Oliva aoliva@redhat.com
33e6b12b 509Ramana Radhakrishnan ramana.radhakrishnan@codito.com
58ad5041 510Frederic Riss frederic.riss@st.com
dfea300e 511Tom Rix trix@redhat.com
e1124681 512Nick Roberts nickrob@snap.net.nz
a8cbc6f7 513Bob Rossi bob_rossi@cox.net
de18ac1f 514Theodore A. Roth troth@openavr.org
627054c8 515Ian Roxborough irox@redhat.com
83b4a0fe 516Grace Sainsbury graces@redhat.com
29ceeffb 517Kei Sakamoto sakamoto.kei@renesas.com
39f0ec5c 518Mark Salter msalter@redhat.com
d738fe6d 519Richard Sandiford richard@codesourcery.com
f4d408c6 520Peter Schauer Peter.Schauer@mytum.de
49d5aff7 521Andreas Schwab schwab@suse.de
f9e2d830 522Keith Seitz keiths@redhat.com
eb944380 523Stan Shebs shebs@apple.com
36479eb1 524Aidan Skinner aidan@velvet.net
5f3b5248 525Jiri Smid smid@suse.cz
e7745bde 526David Smith dsmith@redhat.com
de3a8c23 527Stephen P. Smith ischis2@cox.net
02da6206 528Jackie Smith Cashion jsmith@redhat.com
627054c8 529Michael Snyder msnyder@redhat.com
41ae02c9 530Petr Sorfa petrs@caldera.com
bd73ccbd 531Andrew Stubbs andrew.stubbs@st.com
3517749c 532Ian Lance Taylor ian@airs.com
e7745bde 533Gary Thomas gthomas@redhat.com
12b21d12 534Jason Thorpe thorpej@netbsd.org
f9e2d830 535Tom Tromey tromey@redhat.com
f56c189d 536David Ung davidu@mips.com
0c67cbe9 537D Venkatasubramanian dvenkat@noida.hcltech.com
7717fda3 538Corinna Vinschen vinschen@redhat.com
aedf1c5b 539Keith Walker keith.walker@arm.com
9a3c34fe 540Kris Warkentin kewarken@qnx.com
090ddb2a 541Ulrich Weigand uweigand@de.ibm.com
0b71f08f 542Nathan Williams nathanw@wasabisystems.com
fcd182f9 543Jim Wilson wilson@specifixinc.com
627054c8
AC
544Elena Zannoni ezannoni@redhat.com
545Eli Zaretskii eliz@gnu.org
72429025 546Wu Zhou woodzltc@cn.ibm.com
ba0e80db 547Yoshinori Sato ysato@users.sourceforge.jp
e7745bde 548
15929d05 549
3a0c66d4
AC
550 Past Maintainers
551
f4d408c6
DJ
552Whenever removing yourself, or someone else, from this file, consider
553listing their areas of development here for posterity.
554
47b95330
AC
555Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
556Jeff Law (hppa) law at cygnus dot com
557Daniel Berlin (C++ support) dan at cgsoftware dot com
7fe4d0d2
AC
558Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
559David Taylor (d10v, sparc, utils, defs,
560 expression evaluator, language support) taylor at candd dot org
f4d408c6 561J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
f779ca99 562Frank Ch. Eigler (sim) fche at redhat dot com
8a81a99e 563Per Bothner (Java) per at bothner dot com
23b7d5f3 564Anthony Green (Java) green at redhat dot com
69aec09b 565Fernando Nasser (testsuite/, mi, cli) fnasser at redhat dot com
5aae53e5 566Mark Salter (testsuite/lib+config) msalter at redhat dot com
f4d408c6
DJ
567Jim Kingdon (web pages) kingdon at panix dot com
568Jim Ingham (gdbtk, libgui) jingham at apple dot com
569Mark Kettenis (hurd native) kettenis at gnu dot org
570Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
571Robert Lipe (SCO/Unixware) rjl at sco dot com
572Peter Schauer (global, AIX, xcoffsolib,
573 Solaris/x86) Peter.Schauer at mytum dot de
574Scott Bambrough (ARM) scottb at netwinder dot org
575Philippe De Muyter (coff) phdm at macqel dot be
576Michael Chastain (testsuite) mec.gnu at mindspring dot com
5ecaa7dd 577
3a0c66d4
AC
578
579
e33e9692 580Folks that have been caught up in a paper trail:
dfe25b3a 581
58e23df4 582David Carlton carlton@bactrian.org
This page took 0.385233 seconds and 4 git commands to generate.