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