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.
12 There are four groups of GDB developers, covering the patch development and
15 - The Global Maintainers.
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
22 - The Responsible Maintainers.
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.
28 - The Authorized Committers.
30 These are developers who are trusted to make changes within a specific
31 area of GDB without additional oversight.
33 - The Write After Approval Maintainers.
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
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).
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!
55 There's also a couple of other people who play special roles in the GDB
56 community, separately from the patch process:
58 - The GDB Steering Committee.
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
66 - The Release Manager.
68 This developer is in charge of making new releases of GDB.
70 - The Patch Champions.
72 These volunteers make sure that no contribution is overlooked or
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.
84 All maintainers listed in this file, including the Write After Approval
85 developers, are allowed to check in obvious fixes.
87 An "obvious fix" means that there is no possibility that anyone will
88 disagree with the change.
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. :-)
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.
98 For documentation changes, about the only kind of fix that is obvious
99 is correction of a typo or bad English usage.
102 GDB Steering Committee
103 ----------------------
105 The members of the GDB Steering Committee are the FSF-appointed
106 maintainers of the GDB project.
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
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.
118 Andrew Cagney (Red Hat)
119 Robert Dewar (AdaCore, NYU)
121 Paul Hilfinger (UC Berkeley)
122 Dan Jacobowitz (Google)
123 Stan Shebs (CodeSourcery)
124 Richard Stallman (FSF)
125 Ian Lance Taylor (Google)
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
138 The global maintainers are responsible for reviewing patches to any area
139 for which no Responsible Maintainer is listed.
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.
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
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.
158 The current global maintainers are (in alphabetical order):
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
178 The current release manager is: Joel Brobecker <brobecker@adacore.com>
180 His responsibilities are:
182 * organizing, scheduling, and managing releases of GDB.
184 * deciding the approval and commit policies for release branches,
185 and can change them as needed.
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.
198 Current patch champions (in alphabetical order):
200 Randolph Chung <tausq@debian.org>
204 Responsible Maintainers
205 -----------------------
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.
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.
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).
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.
239 If there are several maintainers for a given domain then any one of them
240 may review a submitted patch.
242 Target Instruction Set Architectures:
244 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
245 (Operating System / Application Binary Interface) issues including CPU
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.
252 alpha --target=alpha-elf ,-Werror
254 arm --target=arm-elf ,-Werror
256 avr --target=avr ,-Werror
257 Tristan Gingold gingold@adacore.com
259 cris --target=cris-elf ,-Werror ,
260 (sim does not build with -Werror)
262 frv --target=frv-elf ,-Werror
264 h8300 --target=h8300-elf ,-Werror
266 i386 --target=i386-elf ,-Werror
267 Mark Kettenis kettenis@gnu.org
269 ia64 --target=ia64-linux-gnu ,-Werror
270 (--target=ia64-elf broken)
272 lm32 --target=lm32-elf ,-Werror
274 m32c --target=m32c-elf ,-Werror
276 m32r --target=m32r-elf ,-Werror
278 m68hc11 --target=m68hc11-elf ,-Werror ,
279 Stephane Carrez stcarrez@nerim.fr
281 m68k --target=m68k-elf ,-Werror
283 m88k --target=m88k-openbsd ,-Werror
284 Mark Kettenis kettenis@gnu.org
288 mep --target=mep-elf ,-Werror
289 Kevin Buettner kevinb@redhat.com
291 microblaze --target=microblaze-xilinx-elf ,-Werror
292 --target=microblaze-linux-gnu ,-Werror
293 Michael Eager eager@eagercon.com
295 mips --target=mips-elf ,-Werror
297 mn10300 --target=mn10300-elf broken
298 (sim/ dies with make -j)
300 moxie --target=moxie-elf ,-Werror
301 Anthony Green green@moxielogic.com
303 ms1 --target=ms1-elf ,-Werror
304 Kevin Buettner kevinb@redhat.com
308 pa --target=hppa-elf ,-Werror
310 powerpc --target=powerpc-eabi ,-Werror
312 rl78 --target=rl78-elf ,-Werror
314 rx --target=rx-elf ,-Werror
316 s390 --target=s390-linux-gnu ,-Werror
318 score --target=score-elf
319 Qinwei qinwei@sunnorth.com.cn
321 sh --target=sh-elf ,-Werror
322 --target=sh64-elf ,-Werror
324 sparc --target=sparc64-solaris2.10 ,-Werror
325 (--target=sparc-elf broken)
327 spu --target=spu-elf ,-Werror
328 Ulrich Weigand uweigand@de.ibm.com
330 tic6x --target=tic6x-elf ,-Werror
331 Yao Qi yao@codesourcery.com
333 v850 --target=v850-elf ,-Werror
335 vax --target=vax-netbsd ,-Werror
337 x86-64 --target=x86_64-linux-gnu ,-Werror
339 xstormy16 --target=xstormy16-elf
340 Corinna Vinschen vinschen@redhat.com
342 xtensa --target=xtensa-elf
343 Maxim Grigoriev maxim2405@gmail.com
345 All developers recognized by this file can make arbitrary changes to
348 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
354 The Native maintainer is responsible for target specific native
355 support - typically shared libraries and quirks to procfs/ptrace/...
356 The Native maintainer works with the Arch and Core maintainers when
357 resolving more generic problems.
359 The host maintainer ensures that gdb can be built as a cross debugger on
362 AIX Joel Brobecker brobecker@adacore.com
363 Darwin Tristan Gingold gingold@adacore.com
364 djgpp native Eli Zaretskii eliz@gnu.org
365 GNU Hurd Alfred M. Szmidt ams@gnu.org
366 MS Windows (NT, '00, 9x, Me, XP) host & native
367 Chris Faylor cgf@alum.bu.edu
368 GNU/Linux/x86 native & host
369 Mark Kettenis kettenis@gnu.org
370 GNU/Linux MIPS native & host
371 Daniel Jacobowitz drow@false.org
372 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
373 FreeBSD native & host Mark Kettenis kettenis@gnu.org
377 Core: Generic components used by all of GDB
379 threads Mark Kettenis kettenis@gnu.org
382 Ada Joel Brobecker brobecker@adacore.com
383 Paul Hilfinger hilfinger@gnat.com
384 C++ Daniel Jacobowitz drow@false.org
385 Objective C support Adam Fedor fedor@gnu.org
386 shared libs Kevin Buettner kevinb@redhat.com
387 MI interface Vladimir Prus vladimir@codesourcery.com
389 documentation Eli Zaretskii eliz@gnu.org
392 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
395 UI: External (user) interfaces.
397 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
398 Keith Seitz keiths@redhat.com
399 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
404 gdb/gdbserver Daniel Jacobowitz drow@false.org
406 Makefile.in, configure* ALL
408 mmalloc/ ALL Host maintainers
410 sim/ See sim/MAINTAINERS
412 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
414 Host maintainers (host dependant parts)
415 (but get your changes into the master version)
420 Authorized Committers
421 ---------------------
423 These are developers working on particular areas of GDB, who are trusted to
424 commit their own (or other developers') patches in those areas without
425 further review from a Global Maintainer or Responsible Maintainer. They are
426 under no obligation to review posted patches - but, of course, are invited
429 PowerPC Andrew Cagney cagney@gnu.org
430 ARM Richard Earnshaw rearnsha@arm.com
431 CRIS Hans-Peter Nilsson hp@axis.com
432 IA64 Jeff Johnston jjohnstn@redhat.com
433 MIPS Joel Brobecker brobecker@adacore.com
434 m32r Kei Sakamoto sakamoto.kei@renesas.com
435 PowerPC Kevin Buettner kevinb@redhat.com
436 CRIS Orjan Friberg orjanf@axis.com
437 HPPA Randolph Chung tausq@debian.org
438 S390 Ulrich Weigand uweigand@de.ibm.com
439 djgpp DJ Delorie dj@delorie.com
440 [Please use this address to contact DJ about DJGPP]
441 tui Stephane Carrez stcarrez@nerim.fr
442 ia64 Kevin Buettner kevinb@redhat.com
443 AIX Kevin Buettner kevinb@redhat.com
444 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
445 gdb.java tests Anthony Green green@redhat.com
446 FreeBSD native & host David O'Brien obrien@freebsd.org
447 event loop Elena Zannoni elena.zannoni@oracle.com
448 generic symtabs Elena Zannoni elena.zannoni@oracle.com
449 dwarf readers Elena Zannoni elena.zannoni@oracle.com
450 elf reader Elena Zannoni elena.zannoni@oracle.com
451 stabs reader Elena Zannoni elena.zannoni@oracle.com
452 readline/ Elena Zannoni elena.zannoni@oracle.com
453 NetBSD native & host Jason Thorpe thorpej@netbsd.org
454 Pascal support Pierre Muller muller@sourceware.org
455 avr Theodore A. Roth troth@openavr.org
456 Modula-2 support Gaius Mulley gaius@glam.ac.uk
462 To get recommended for the Write After Approval list you need a valid
463 FSF assignment and have submitted one good patch.
465 Pedro Alves pedro_alves@portugalmail.pt
466 David Anderson davea@sgi.com
467 John David Anglin dave.anglin@nrc-cnrc.gc.ca
468 Shrinivas Atre shrinivasa@kpitcummins.com
469 Sterling Augustine saugustine@google.com
470 Scott Bambrough scottb@netwinder.org
471 Thiago Jung Bauermann bauerman@br.ibm.com
472 Jon Beniston jon@beniston.com
473 Gary Benson gbenson@redhat.com
474 Jan Beulich jbeulich@novell.com
475 Jim Blandy jimb@codesourcery.com
476 Philip Blundell philb@gnu.org
477 Eric Botcazou ebotcazou@libertysurf.fr
478 Per Bothner per@bothner.com
479 Joel Brobecker brobecker@adacore.com
480 Dave Brolley brolley@redhat.com
481 Paul Brook paul@codesourcery.com
482 Julian Brown julian@codesourcery.com
483 Kevin Buettner kevinb@redhat.com
484 Andrew Burgess aburgess@broadcom.com
485 Andrew Cagney cagney@gnu.org
486 David Carlton carlton@bactrian.org
487 Stephane Carrez stcarrez@nerim.fr
488 Michael Chastain mec.gnu@mindspring.com
489 Renquan Cheng crq@gcc.gnu.org
490 Eric Christopher echristo@apple.com
491 Randolph Chung tausq@debian.org
492 Nick Clifton nickc@redhat.com
493 J.T. Conklin jtc@acorntoolworks.com
494 Brendan Conoboy blc@redhat.com
495 Ludovic Courtès ludo@gnu.org
496 Sanjoy Das sanjoy@playingwithpointers.com
497 Jean-Charles Delay delay@adacore.com
498 DJ Delorie dj@redhat.com
499 Chris Demetriou cgd@google.com
500 Philippe De Muyter phdm@macqel.be
501 Dhananjay Deshpande dhananjayd@kpitcummins.com
502 Markus Deuling deuling@de.ibm.com
503 Klee Dienes kdienes@apple.com
504 Gabriel Dos Reis gdr@integrable-solutions.net
505 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
506 Michael Eager eager@eagercon.com
507 Richard Earnshaw rearnsha@arm.com
508 Steve Ellcey sje@cup.hp.com
509 Frank Ch. Eigler fche@redhat.com
510 Ben Elliston bje@gnu.org
511 Doug Evans dje@google.com
512 Adam Fedor fedor@gnu.org
513 Brian Ford ford@vss.fsi.com
514 Orjan Friberg orjanf@axis.com
515 Nathan Froyd froydnj@codesourcery.com
516 Gary Funck gary@intrepid.com
517 Paul Gilliam pgilliam@us.ibm.com
518 Tristan Gingold gingold@adacore.com
519 Raoul Gough RaoulGough@yahoo.co.uk
520 Anthony Green green@redhat.com
521 Matthew Green mrg@eterna.com.au
522 Matthew Gretton-Dann matthew.gretton-dann@arm.com
523 Maxim Grigoriev maxim2405@gmail.com
524 Jerome Guitton guitton@act-europe.fr
525 Ben Harris bjh21@netbsd.org
526 Richard Henderson rth@redhat.com
527 Aldy Hernandez aldyh@redhat.com
528 Paul Hilfinger hilfinger@gnat.com
529 Matt Hiller hiller@redhat.com
530 Kazu Hirata kazu@cs.umass.edu
531 Jeff Holcomb jeffh@redhat.com
532 Don Howard dhoward@redhat.com
533 Nick Hudson nick.hudson@dsl.pipex.com
534 Martin Hunt hunt@redhat.com
535 Meador Inge meadori@codesourcery.com
536 Jim Ingham jingham@apple.com
537 Baurzhan Ismagulov ibr@radix50.net
538 Manoj Iyer manjo@austin.ibm.com
539 Daniel Jacobowitz drow@false.org
540 Andreas Jaeger aj@suse.de
541 Janis Johnson janisjo@codesourcery.com
542 Jeff Johnston jjohnstn@redhat.com
543 Geoff Keating geoffk@redhat.com
544 Mark Kettenis kettenis@gnu.org
545 Marc Khouzam marc.khouzam@ericsson.com
546 Jim Kingdon kingdon@panix.com
547 Paul Koning paul_koning@dell.com
548 Jan Kratochvil jan.kratochvil@redhat.com
549 Jonathan Larmour jifl@ecoscentric.com
550 Jeff Law law@redhat.com
551 Justin Lebar justin.lebar@gmail.com
552 David Lecomber david@streamline-computing.com
553 Don Lee don.lee@sunplusct.com
554 Robert Lipe rjl@sco.com
555 Sandra Loosemore sandra@codesourcery.com
556 H.J. Lu hjl.tools@gmail.com
557 Michal Ludvig mludvig@suse.cz
558 Edjunior B. Machado emachado@linux.vnet.ibm.com
559 Luis Machado lgustavo@codesourcery.com
560 Glen McCready gkm@redhat.com
561 Greg McGary greg@mcgary.org
562 Roland McGrath roland@redhat.com
563 Bryce McKinlay mckinlay@redhat.com
564 Jason Merrill jason@redhat.com
565 David S. Miller davem@redhat.com
566 Mark Mitchell mark@codesourcery.com
567 Marko Mlinar markom@opencores.org
568 Alan Modra amodra@gmail.com
569 Fawzi Mohamed fawzi.mohamed@nokia.com
570 Jason Molenda jmolenda@apple.com
571 Chris Moller cmoller@redhat.com
572 Phil Muldoon pmuldoon@redhat.com
573 Pierre Muller muller@sourceware.org
574 Gaius Mulley gaius@glam.ac.uk
575 Masaki Muranaka monaka@monami-software.com
576 Joseph Myers joseph@codesourcery.com
577 Fernando Nasser fnasser@redhat.com
578 Adam Nemet anemet@caviumnetworks.com
579 Nathanael Nerode neroden@gcc.gnu.org
580 Hans-Peter Nilsson hp@bitrange.com
581 David O'Brien obrien@freebsd.org
582 Alexandre Oliva aoliva@redhat.com
583 Karen Osmond karen.osmond@gmail.com
584 Denis Pilat denis.pilat@st.com
585 Kevin Pouget kevin.pouget@st.com
586 Paul Pluzhnikov ppluzhnikov@google.com
587 Marek Polacek mpolacek@redhat.com
588 Vladimir Prus vladimir@codesourcery.com
589 Yao Qi yao@codesourcery.com
590 Qinwei qinwei@sunnorth.com.cn
591 Matt Rice ratmice@gmail.com
592 Frederic Riss frederic.riss@st.com
593 Aleksandar Ristovski aristovski@qnx.com
594 Tom Rix trix@redhat.com
595 Nick Roberts nickrob@snap.net.nz
596 Bob Rossi bob_rossi@cox.net
597 Theodore A. Roth troth@openavr.org
598 Ian Roxborough irox@redhat.com
599 Maciej W. Rozycki macro@linux-mips.org
600 Grace Sainsbury graces@redhat.com
601 Kei Sakamoto sakamoto.kei@renesas.com
602 Mark Salter msalter@redhat.com
603 Richard Sandiford richard@codesourcery.com
604 Peter Schauer Peter.Schauer@mytum.de
605 Andreas Schwab schwab@linux-m68k.org
606 Thomas Schwinge tschwinge@gnu.org
607 Keith Seitz keiths@redhat.com
608 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
609 Ozkan Sezer sezeroz@gmail.com
610 Stan Shebs stan@codesourcery.com
611 Joel Sherrill joel.sherrill@oarcorp.com
612 Mark Shinwell shinwell@codesourcery.com
613 Craig Silverstein csilvers@google.com
614 Aidan Skinner aidan@velvet.net
615 Jiri Smid smid@suse.cz
616 Andrey Smirnov andrew.smirnov@gmail.com
617 David Smith dsmith@redhat.com
618 Stephen P. Smith ischis2@cox.net
619 Jackie Smith Cashion jsmith@redhat.com
620 Petr Sorfa petrs@caldera.com
621 Andrew Stubbs ams@codesourcery.com
622 Emi Suzuki emi-suzuki@tjsys.co.jp
623 Ian Lance Taylor ian@airs.com
624 Gary Thomas gthomas@redhat.com
625 Jason Thorpe thorpej@netbsd.org
626 Caroline Tice ctice@apple.com
627 Kai Tietz ktietz@redhat.com
628 Andreas Tobler andreast@fgznet.ch
629 Tom Tromey tromey@redhat.com
630 David Ung davidu@mips.com
631 D Venkatasubramanian dvenkat@noida.hcltech.com
632 Corinna Vinschen vinschen@redhat.com
633 Sami Wagiaalla swagiaal@redhat.com
634 Keith Walker keith.walker@arm.com
635 Kris Warkentin kewarken@qnx.com
636 Philippe Waroquiers philippe.waroquiers@skynet.be
637 Ulrich Weigand uweigand@de.ibm.com
638 Ken Werner ken.werner@de.ibm.com
639 Nathan Williams nathanw@wasabisystems.com
640 Bob Wilson bob.wilson@acm.org
641 Jim Wilson wilson@tuliptree.org
642 Kwok Cheung Yeung kcy@codesourcery.com
643 Elena Zannoni elena.zannoni@oracle.com
644 Eli Zaretskii eliz@gnu.org
645 Jie Zhang jzhang918@gmail.com
646 Wu Zhou woodzltc@cn.ibm.com
647 Yoshinori Sato ysato@users.sourceforge.jp
648 Hui Zhu teawater@gmail.com
653 Whenever removing yourself, or someone else, from this file, consider
654 listing their areas of development here for posterity.
656 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
657 Jeff Law (hppa) law at cygnus dot com
658 Daniel Berlin (C++ support) dan at cgsoftware dot com
659 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
660 David Taylor (d10v, sparc, utils, defs,
661 expression evaluator, language support) taylor at candd dot org
662 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
663 Frank Ch. Eigler (sim) fche at redhat dot com
664 Per Bothner (Java) per at bothner dot com
665 Anthony Green (Java) green at redhat dot com
666 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
667 Mark Salter (testsuite/lib+config) msalter at redhat dot com
668 Jim Kingdon (web pages) kingdon at panix dot com
669 Jim Ingham (gdbtk, libgui) jingham at apple dot com
670 Mark Kettenis (hurd native) kettenis at gnu dot org
671 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
672 Robert Lipe (SCO/Unixware) rjl at sco dot com
673 Peter Schauer (global, AIX, xcoffsolib,
674 Solaris/x86) Peter.Schauer at mytum dot de
675 Scott Bambrough (ARM) scottb at netwinder dot org
676 Philippe De Muyter (coff) phdm at macqel dot be
677 Michael Chastain (testsuite) mec.gnu at mindspring dot com
679 Jim Blandy (global) jimb@red-bean.com
680 Michael Snyder (global)
683 Folks that have been caught up in a paper trail:
685 David Carlton carlton@bactrian.org
686 Ramana Radhakrishnan ramana.r@gmail.com