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