projects / binutils-gdb.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
history | raw | HEAD
2012-01-09 Pedro Alves <palves@redhat.com>
[binutils-gdb.git] / gdb / MAINTAINERS
1 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 Andrew Cagney (Red Hat)
119 Robert Dewar (AdaCore, NYU)
120 Klee Dienes (Apple)
121 Paul Hilfinger (UC Berkeley)
122 Dan Jacobowitz (Google)
123 Stan Shebs (CodeSourcery)
124 Richard Stallman (FSF)
125 Ian Lance Taylor (Google)
126 Todd Whitesel
127
128
129 Global Maintainers
130 ------------------
131
132 The global maintainers may review and commit any change to GDB, except in
133 areas with a Responsible Maintainer available. For major changes, or
134 changes to areas with other active developers, global maintainers are
135 strongly encouraged to post their own patches for feedback before
136 committing.
137
138 The global maintainers are responsible for reviewing patches to any area
139 for which no Responsible Maintainer is listed.
140
141 Global maintainers also have the authority to revert patches which should
142 not have been applied, e.g. patches which were not approved, controversial
143 patches committed under the Obvious Fix Rule, patches with important bugs
144 that can't be immediately fixed, or patches which go against an accepted and
145 documented roadmap for GDB development. Any global maintainer may request
146 the reversion of a patch. If no global maintainer, or responsible
147 maintainer in the affected areas, supports the patch (except for the
148 maintainer who originally committed it), then after 48 hours the maintainer
149 who called for the reversion may revert the patch.
150
151 No one may reapply a reverted patch without the agreement of the maintainer
152 who reverted it, or bringing the issue to the GDB Steering Committee for
153 discussion.
154
155 At the moment there are no documented roadmaps for GDB development; in the
156 future, if there are, a reference to the list will be included here.
157
158 The current global maintainers are (in alphabetical order):
159
160 Pedro Alves palves@redhat.com
161 Joel Brobecker brobecker@adacore.com
162 Kevin Buettner kevinb@redhat.com
163 Andrew Cagney cagney@gnu.org
164 Doug Evans dje@google.com
165 Daniel Jacobowitz drow@false.org
166 Mark Kettenis kettenis@gnu.org
167 Jan Kratochvil jan.kratochvil@redhat.com
168 Stan Shebs stan@codesourcery.com
169 Tom Tromey tromey@redhat.com
170 Ulrich Weigand Ulrich.Weigand@de.ibm.com
171 Elena Zannoni elena.zannoni@oracle.com
172 Eli Zaretskii eliz@gnu.org
173
174
175 Release Manager
176 ---------------
177
178 The current release manager is: Joel Brobecker <brobecker@adacore.com>
179
180 His responsibilities are:
181
182 * organizing, scheduling, and managing releases of GDB.
183
184 * deciding the approval and commit policies for release branches,
185 and can change them as needed.
186
187
188
189 Patch Champions
190 ---------------
191
192 These volunteers track all patches submitted to the gdb-patches list. They
193 endeavor to prevent any posted patch from being overlooked; work with
194 contributors to meet GDB's coding style and general requirements, along with
195 FSF copyright assignments; remind (ping) responsible maintainers to review
196 patches; and ensure that contributors are given credit.
197
198 Current patch champions (in alphabetical order):
199
200 Randolph Chung <tausq@debian.org>
201
202
203
204 Responsible Maintainers
205 -----------------------
206
207 These developers have agreed to review patches in specific areas of GDB, in
208 which they have knowledge and experience. These areas are generally broad;
209 the role of a responsible maintainer is to provide coherent and cohesive
210 structure within their area of GDB, to assure that patches from many
211 different contributors all work together for the best results.
212
213 Global maintainers will defer to responsible maintainers within their areas,
214 as long as the responsible maintainer is active. Active means that
215 responsible maintainers agree to review submitted patches in their area
216 promptly; patches and followups should generally be answered within a week.
217 If a responsible maintainer is interested in reviewing a patch but will not
218 have time within a week of posting, the maintainer should send an
219 acknowledgement of the patch to the gdb-patches mailing list, and
220 plan to follow up with a review within a month. These deadlines are for
221 initial responses to a patch - if the maintainer has suggestions
222 or questions, it may take an extended discussion before the patch
223 is ready to commit. There are no written requirements for discussion,
224 but maintainers are asked to be responsive.
225
226 If a responsible maintainer misses these deadlines occasionally (e.g.
227 vacation or unexpected workload), it's not a disaster - any global
228 maintainer may step in to review the patch. But sometimes life intervenes
229 more permanently, and a maintainer may no longer have time for these duties.
230 When this happens, he or she should step down (either into the Authorized
231 Committers section if still interested in the area, or simply removed from
232 the list of Responsible Maintainers if not).
233
234 If a responsible maintainer is unresponsive for an extended period of time
235 without stepping down, please contact the Global Maintainers; they will try
236 to contact the maintainer directly and fix the problem - potentially by
237 removing that maintainer from their listed position.
238
239 If there are several maintainers for a given domain then any one of them
240 may review a submitted patch.
241
242 Target Instruction Set Architectures:
243
244 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
245 (Operating System / Application Binary Interface) issues including CPU
246 variants.
247
248 The Target/Architecture maintainer works with the host maintainer when
249 resolving build issues. The Target/Architecture maintainer works with
250 the native maintainer when resolving ABI issues.
251
252 alpha --target=alpha-elf ,-Werror
253
254 arm --target=arm-elf ,-Werror
255
256 avr --target=avr ,-Werror
257 Tristan Gingold gingold@adacore.com
258
259 cris --target=cris-elf ,-Werror ,
260 (sim does not build with -Werror)
261
262 frv --target=frv-elf ,-Werror
263
264 h8300 --target=h8300-elf ,-Werror
265
266 i386 --target=i386-elf ,-Werror
267 Mark Kettenis kettenis@gnu.org
268
269 ia64 --target=ia64-linux-gnu ,-Werror
270 (--target=ia64-elf broken)
271 Jan Kratochvil jan.kratochvil@redhat.com
272
273 lm32 --target=lm32-elf ,-Werror
274
275 m32c --target=m32c-elf ,-Werror
276
277 m32r --target=m32r-elf ,-Werror
278
279 m68hc11 --target=m68hc11-elf ,-Werror ,
280 Stephane Carrez stcarrez@nerim.fr
281
282 m68k --target=m68k-elf ,-Werror
283
284 m88k --target=m88k-openbsd ,-Werror
285 Mark Kettenis kettenis@gnu.org
286
287 mcore Deleted
288
289 mep --target=mep-elf ,-Werror
290 Kevin Buettner kevinb@redhat.com
291
292 microblaze --target=microblaze-xilinx-elf ,-Werror
293 --target=microblaze-linux-gnu ,-Werror
294 Michael Eager eager@eagercon.com
295
296 mips --target=mips-elf ,-Werror
297
298 mn10300 --target=mn10300-elf broken
299 (sim/ dies with make -j)
300
301 moxie --target=moxie-elf ,-Werror
302 Anthony Green green@moxielogic.com
303
304 ms1 --target=ms1-elf ,-Werror
305 Kevin Buettner kevinb@redhat.com
306
307 ns32k Deleted
308
309 pa --target=hppa-elf ,-Werror
310
311 powerpc --target=powerpc-eabi ,-Werror
312
313 s390 --target=s390-linux-gnu ,-Werror
314
315 score --target=score-elf
316 Qinwei qinwei@sunnorth.com.cn
317
318 sh --target=sh-elf ,-Werror
319 --target=sh64-elf ,-Werror
320
321 sparc --target=sparc64-solaris2.10 ,-Werror
322 (--target=sparc-elf broken)
323
324 spu --target=spu-elf ,-Werror
325 Ulrich Weigand uweigand@de.ibm.com
326
327 tic6x --target=tic6x-elf ,-Werror
328 Yao Qi yao@codesourcery.com
329
330 v850 --target=v850-elf ,-Werror
331
332 vax --target=vax-netbsd ,-Werror
333
334 x86-64 --target=x86_64-linux-gnu ,-Werror
335
336 xstormy16 --target=xstormy16-elf
337 Corinna Vinschen vinschen@redhat.com
338
339 xtensa --target=xtensa-elf
340 Maxim Grigoriev maxim2405@gmail.com
341
342 All developers recognized by this file can make arbitrary changes to
343 OBSOLETE targets.
344
345 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
346 above targets.
347
348
349 Host/Native:
350
351 The Native maintainer is responsible for target specific native
352 support - typically shared libraries and quirks to procfs/ptrace/...
353 The Native maintainer works with the Arch and Core maintainers when
354 resolving more generic problems.
355
356 The host maintainer ensures that gdb can be built as a cross debugger on
357 their platform.
358
359 AIX Joel Brobecker brobecker@adacore.com
360 Darwin Tristan Gingold gingold@adacore.com
361 djgpp native Eli Zaretskii eliz@gnu.org
362 GNU Hurd Alfred M. Szmidt ams@gnu.org
363 MS Windows (NT, '00, 9x, Me, XP) host & native
364 Chris Faylor cgf@alum.bu.edu
365 GNU/Linux/x86 native & host
366 Mark Kettenis kettenis@gnu.org
367 GNU/Linux MIPS native & host
368 Daniel Jacobowitz drow@false.org
369 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
370 FreeBSD native & host Mark Kettenis kettenis@gnu.org
371
372
373
374 Core: Generic components used by all of GDB
375
376 threads Mark Kettenis kettenis@gnu.org
377
378 language support
379 Ada Joel Brobecker brobecker@adacore.com
380 Paul Hilfinger hilfinger@gnat.com
381 C++ Daniel Jacobowitz drow@false.org
382 Objective C support Adam Fedor fedor@gnu.org
383 shared libs Kevin Buettner kevinb@redhat.com
384 MI interface Vladimir Prus vladimir@codesourcery.com
385
386 documentation Eli Zaretskii eliz@gnu.org
387 (including NEWS)
388 testsuite
389 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
390
391
392 UI: External (user) interfaces.
393
394 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
395 Keith Seitz keiths@redhat.com
396 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
397
398
399 Misc:
400
401 gdb/gdbserver Daniel Jacobowitz drow@false.org
402
403 Makefile.in, configure* ALL
404
405 mmalloc/ ALL Host maintainers
406
407 sim/ See sim/MAINTAINERS
408
409 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
410 ALL
411 Host maintainers (host dependant parts)
412 (but get your changes into the master version)
413
414 tcl/ tk/ itcl/ ALL
415
416
417 Authorized Committers
418 ---------------------
419
420 These are developers working on particular areas of GDB, who are trusted to
421 commit their own (or other developers') patches in those areas without
422 further review from a Global Maintainer or Responsible Maintainer. They are
423 under no obligation to review posted patches - but, of course, are invited
424 to do so!
425
426 PowerPC Andrew Cagney cagney@gnu.org
427 ARM Richard Earnshaw rearnsha@arm.com
428 CRIS Hans-Peter Nilsson hp@axis.com
429 IA64 Jeff Johnston jjohnstn@redhat.com
430 MIPS Joel Brobecker brobecker@adacore.com
431 m32r Kei Sakamoto sakamoto.kei@renesas.com
432 PowerPC Kevin Buettner kevinb@redhat.com
433 CRIS Orjan Friberg orjanf@axis.com
434 HPPA Randolph Chung tausq@debian.org
435 S390 Ulrich Weigand uweigand@de.ibm.com
436 djgpp DJ Delorie dj@delorie.com
437 [Please use this address to contact DJ about DJGPP]
438 tui Stephane Carrez stcarrez@nerim.fr
439 ia64 Kevin Buettner kevinb@redhat.com
440 AIX Kevin Buettner kevinb@redhat.com
441 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
442 gdb.java tests Anthony Green green@redhat.com
443 FreeBSD native & host David O'Brien obrien@freebsd.org
444 event loop Elena Zannoni elena.zannoni@oracle.com
445 generic symtabs Elena Zannoni elena.zannoni@oracle.com
446 dwarf readers Elena Zannoni elena.zannoni@oracle.com
447 elf reader Elena Zannoni elena.zannoni@oracle.com
448 stabs reader Elena Zannoni elena.zannoni@oracle.com
449 readline/ Elena Zannoni elena.zannoni@oracle.com
450 NetBSD native & host Jason Thorpe thorpej@netbsd.org
451 Pascal support Pierre Muller muller@sourceware.org
452 avr Theodore A. Roth troth@openavr.org
453 Modula-2 support Gaius Mulley gaius@glam.ac.uk
454
455
456 Write After Approval
457 (alphabetic)
458
459 To get recommended for the Write After Approval list you need a valid
460 FSF assignment and have submitted one good patch.
461
462 Pedro Alves pedro_alves@portugalmail.pt
463 David Anderson davea@sgi.com
464 John David Anglin dave.anglin@nrc-cnrc.gc.ca
465 Shrinivas Atre shrinivasa@kpitcummins.com
466 Sterling Augustine saugustine@google.com
467 Scott Bambrough scottb@netwinder.org
468 Thiago Jung Bauermann bauerman@br.ibm.com
469 Jon Beniston jon@beniston.com
470 Gary Benson gbenson@redhat.com
471 Jan Beulich jbeulich@novell.com
472 Jim Blandy jimb@codesourcery.com
473 Philip Blundell philb@gnu.org
474 Eric Botcazou ebotcazou@libertysurf.fr
475 Per Bothner per@bothner.com
476 Joel Brobecker brobecker@adacore.com
477 Dave Brolley brolley@redhat.com
478 Paul Brook paul@codesourcery.com
479 Julian Brown julian@codesourcery.com
480 Kevin Buettner kevinb@redhat.com
481 Andrew Burgess aburgess@broadcom.com
482 Andrew Cagney cagney@gnu.org
483 David Carlton carlton@bactrian.org
484 Stephane Carrez stcarrez@nerim.fr
485 Michael Chastain mec.gnu@mindspring.com
486 Renquan Cheng crq@gcc.gnu.org
487 Eric Christopher echristo@apple.com
488 Randolph Chung tausq@debian.org
489 Nick Clifton nickc@redhat.com
490 J.T. Conklin jtc@acorntoolworks.com
491 Brendan Conoboy blc@redhat.com
492 Ludovic Courtès ludo@gnu.org
493 Sanjoy Das sanjoy@playingwithpointers.com
494 Jean-Charles Delay delay@adacore.com
495 DJ Delorie dj@redhat.com
496 Chris Demetriou cgd@google.com
497 Philippe De Muyter phdm@macqel.be
498 Dhananjay Deshpande dhananjayd@kpitcummins.com
499 Markus Deuling deuling@de.ibm.com
500 Klee Dienes kdienes@apple.com
501 Gabriel Dos Reis gdr@integrable-solutions.net
502 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
503 Michael Eager eager@eagercon.com
504 Richard Earnshaw rearnsha@arm.com
505 Steve Ellcey sje@cup.hp.com
506 Frank Ch. Eigler fche@redhat.com
507 Ben Elliston bje@gnu.org
508 Doug Evans dje@google.com
509 Adam Fedor fedor@gnu.org
510 Brian Ford ford@vss.fsi.com
511 Orjan Friberg orjanf@axis.com
512 Nathan Froyd froydnj@codesourcery.com
513 Gary Funck gary@intrepid.com
514 Paul Gilliam pgilliam@us.ibm.com
515 Tristan Gingold gingold@adacore.com
516 Raoul Gough RaoulGough@yahoo.co.uk
517 Anthony Green green@redhat.com
518 Matthew Green mrg@eterna.com.au
519 Matthew Gretton-Dann matthew.gretton-dann@arm.com
520 Maxim Grigoriev maxim2405@gmail.com
521 Jerome Guitton guitton@act-europe.fr
522 Ben Harris bjh21@netbsd.org
523 Richard Henderson rth@redhat.com
524 Aldy Hernandez aldyh@redhat.com
525 Paul Hilfinger hilfinger@gnat.com
526 Matt Hiller hiller@redhat.com
527 Kazu Hirata kazu@cs.umass.edu
528 Jeff Holcomb jeffh@redhat.com
529 Don Howard dhoward@redhat.com
530 Nick Hudson nick.hudson@dsl.pipex.com
531 Martin Hunt hunt@redhat.com
532 Meador Inge meadori@codesourcery.com
533 Jim Ingham jingham@apple.com
534 Baurzhan Ismagulov ibr@radix50.net
535 Manoj Iyer manjo@austin.ibm.com
536 Daniel Jacobowitz drow@false.org
537 Andreas Jaeger aj@suse.de
538 Janis Johnson janisjo@codesourcery.com
539 Jeff Johnston jjohnstn@redhat.com
540 Geoff Keating geoffk@redhat.com
541 Mark Kettenis kettenis@gnu.org
542 Marc Khouzam marc.khouzam@ericsson.com
543 Jim Kingdon kingdon@panix.com
544 Paul Koning paul_koning@dell.com
545 Jan Kratochvil jan.kratochvil@redhat.com
546 Jonathan Larmour jifl@ecoscentric.com
547 Jeff Law law@redhat.com
548 Justin Lebar justin.lebar@gmail.com
549 David Lecomber david@streamline-computing.com
550 Don Lee don.lee@sunplusct.com
551 Robert Lipe rjl@sco.com
552 Sandra Loosemore sandra@codesourcery.com
553 H.J. Lu hjl.tools@gmail.com
554 Michal Ludvig mludvig@suse.cz
555 Edjunior B. Machado emachado@linux.vnet.ibm.com
556 Luis Machado lgustavo@codesourcery.com
557 Glen McCready gkm@redhat.com
558 Greg McGary greg@mcgary.org
559 Roland McGrath roland@redhat.com
560 Bryce McKinlay mckinlay@redhat.com
561 Jason Merrill jason@redhat.com
562 David S. Miller davem@redhat.com
563 Mark Mitchell mark@codesourcery.com
564 Marko Mlinar markom@opencores.org
565 Alan Modra amodra@gmail.com
566 Fawzi Mohamed fawzi.mohamed@nokia.com
567 Jason Molenda jmolenda@apple.com
568 Chris Moller cmoller@redhat.com
569 Phil Muldoon pmuldoon@redhat.com
570 Pierre Muller muller@sourceware.org
571 Gaius Mulley gaius@glam.ac.uk
572 Masaki Muranaka monaka@monami-software.com
573 Joseph Myers joseph@codesourcery.com
574 Fernando Nasser fnasser@redhat.com
575 Adam Nemet anemet@caviumnetworks.com
576 Nathanael Nerode neroden@gcc.gnu.org
577 Hans-Peter Nilsson hp@bitrange.com
578 David O'Brien obrien@freebsd.org
579 Alexandre Oliva aoliva@redhat.com
580 Karen Osmond karen.osmond@gmail.com
581 Denis Pilat denis.pilat@st.com
582 Kevin Pouget kevin.pouget@st.com
583 Paul Pluzhnikov ppluzhnikov@google.com
584 Marek Polacek mpolacek@redhat.com
585 Vladimir Prus vladimir@codesourcery.com
586 Yao Qi yao@codesourcery.com
587 Qinwei qinwei@sunnorth.com.cn
588 Matt Rice ratmice@gmail.com
589 Frederic Riss frederic.riss@st.com
590 Aleksandar Ristovski aristovski@qnx.com
591 Tom Rix trix@redhat.com
592 Nick Roberts nickrob@snap.net.nz
593 Bob Rossi bob_rossi@cox.net
594 Theodore A. Roth troth@openavr.org
595 Ian Roxborough irox@redhat.com
596 Maciej W. Rozycki macro@linux-mips.org
597 Grace Sainsbury graces@redhat.com
598 Kei Sakamoto sakamoto.kei@renesas.com
599 Mark Salter msalter@redhat.com
600 Richard Sandiford richard@codesourcery.com
601 Peter Schauer Peter.Schauer@mytum.de
602 Andreas Schwab schwab@linux-m68k.org
603 Thomas Schwinge tschwinge@gnu.org
604 Keith Seitz keiths@redhat.com
605 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
606 Ozkan Sezer sezeroz@gmail.com
607 Stan Shebs stan@codesourcery.com
608 Joel Sherrill joel.sherrill@oarcorp.com
609 Mark Shinwell shinwell@codesourcery.com
610 Craig Silverstein csilvers@google.com
611 Aidan Skinner aidan@velvet.net
612 Jiri Smid smid@suse.cz
613 Andrey Smirnov andrew.smirnov@gmail.com
614 David Smith dsmith@redhat.com
615 Stephen P. Smith ischis2@cox.net
616 Jackie Smith Cashion jsmith@redhat.com
617 Petr Sorfa petrs@caldera.com
618 Andrew Stubbs ams@codesourcery.com
619 Emi Suzuki emi-suzuki@tjsys.co.jp
620 Ian Lance Taylor ian@airs.com
621 Gary Thomas gthomas@redhat.com
622 Jason Thorpe thorpej@netbsd.org
623 Caroline Tice ctice@apple.com
624 Kai Tietz ktietz@redhat.com
625 Andreas Tobler andreast@fgznet.ch
626 Tom Tromey tromey@redhat.com
627 David Ung davidu@mips.com
628 D Venkatasubramanian dvenkat@noida.hcltech.com
629 Corinna Vinschen vinschen@redhat.com
630 Sami Wagiaalla swagiaal@redhat.com
631 Keith Walker keith.walker@arm.com
632 Kris Warkentin kewarken@qnx.com
633 Philippe Waroquiers philippe.waroquiers@skynet.be
634 Ulrich Weigand uweigand@de.ibm.com
635 Ken Werner ken.werner@de.ibm.com
636 Nathan Williams nathanw@wasabisystems.com
637 Bob Wilson bob.wilson@acm.org
638 Jim Wilson wilson@tuliptree.org
639 Kwok Cheung Yeung kcy@codesourcery.com
640 Elena Zannoni elena.zannoni@oracle.com
641 Eli Zaretskii eliz@gnu.org
642 Jie Zhang jzhang918@gmail.com
643 Wu Zhou woodzltc@cn.ibm.com
644 Yoshinori Sato ysato@users.sourceforge.jp
645 Hui Zhu teawater@gmail.com
646
647
648 Past Maintainers
649
650 Whenever removing yourself, or someone else, from this file, consider
651 listing their areas of development here for posterity.
652
653 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
654 Jeff Law (hppa) law at cygnus dot com
655 Daniel Berlin (C++ support) dan at cgsoftware dot com
656 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
657 David Taylor (d10v, sparc, utils, defs,
658 expression evaluator, language support) taylor at candd dot org
659 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
660 Frank Ch. Eigler (sim) fche at redhat dot com
661 Per Bothner (Java) per at bothner dot com
662 Anthony Green (Java) green at redhat dot com
663 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
664 Mark Salter (testsuite/lib+config) msalter at redhat dot com
665 Jim Kingdon (web pages) kingdon at panix dot com
666 Jim Ingham (gdbtk, libgui) jingham at apple dot com
667 Mark Kettenis (hurd native) kettenis at gnu dot org
668 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
669 Robert Lipe (SCO/Unixware) rjl at sco dot com
670 Peter Schauer (global, AIX, xcoffsolib,
671 Solaris/x86) Peter.Schauer at mytum dot de
672 Scott Bambrough (ARM) scottb at netwinder dot org
673 Philippe De Muyter (coff) phdm at macqel dot be
674 Michael Chastain (testsuite) mec.gnu at mindspring dot com
675 Fred Fish (global)
676 Jim Blandy (global) jimb@red-bean.com
677 Michael Snyder (global)
678
679
680 Folks that have been caught up in a paper trail:
681
682 David Carlton carlton@bactrian.org
683 Ramana Radhakrishnan ramana.r@gmail.com
684
685 ;; Local Variables:
686 ;; coding: utf-8
687 ;; End: