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