projects / binutils-gdb.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
history | raw | HEAD
* MAINTAINERS: Remove self as m32c target maintainer.
[binutils-gdb.git] / gdb / MAINTAINERS
1 GDB Maintainers
2 ===============
3
4
5 Overview
6 --------
7
8 This file describes different groups of people who are, together, the
9 maintainers and developers of the GDB project. Don't worry - it sounds
10 more complicated than it really is.
11
12 There are four groups of GDB developers, covering the patch development and
13 review process:
14
15 - The Global Maintainers.
16
17 These are the developers in charge of most daily development. They
18 have wide authority to apply and reject patches, but defer to the
19 Responsible Maintainers (see below) within their spheres of
20 responsibility.
21
22 - The Responsible Maintainers.
23
24 These are developers who have expertise and interest in a particular
25 area of GDB, who are generally available to review patches, and who
26 prefer to enforce a single vision within their areas.
27
28 - The Authorized Committers.
29
30 These are developers who are trusted to make changes within a specific
31 area of GDB without additional oversight.
32
33 - The Write After Approval Maintainers.
34
35 These are developers who have write access to the GDB source tree. They
36 can check in their own changes once a developer with the appropriate
37 authority has approved the changes; they can also apply the Obvious
38 Fix Rule (below).
39
40 All maintainers are encouraged to post major patches to the gdb-patches
41 mailing list for comments, even if they have the authority to commit the
42 patch without review from another maintainer. This especially includes
43 patches which change internal interfaces (e.g. global functions, data
44 structures) or external interfaces (e.g. user, remote, MI, et cetera).
45
46 The term "review" is used in this file to describe several kinds of feedback
47 from a maintainer: approval, rejection, and requests for changes or
48 clarification with the intention of approving a revised version. Review is
49 a privilege and/or responsibility of various positions among the GDB
50 Maintainers. Of course, anyone - whether they hold a position but not the
51 relevant one for a particular patch, or are just following along on the
52 mailing lists for fun, or anything in between - may suggest changes or
53 ask questions about a patch!
54
55 There's also a couple of other people who play special roles in the GDB
56 community, separately from the patch process:
57
58 - The GDB Steering Committee.
59
60 These are the official (FSF-appointed) maintainers of GDB. They have
61 final and overriding authority for all GDB-related decisions, including
62 anything described in this file. The committee is not generally
63 involved in day-to-day development (although its members may be, as
64 individuals).
65
66 - The Release Manager.
67
68 This developer is in charge of making new releases of GDB.
69
70 - The Patch Champions.
71
72 These volunteers make sure that no contribution is overlooked or
73 forgotten.
74
75 Most changes to the list of maintainers in this file are handled by
76 consensus among the global maintainers and any other involved parties.
77 In cases where consensus can not be reached, the global maintainers may
78 ask the Steering Committee for a final decision.
79
80
81 The Obvious Fix Rule
82 --------------------
83
84 All maintainers listed in this file, including the Write After Approval
85 developers, are allowed to check in obvious fixes.
86
87 An "obvious fix" means that there is no possibility that anyone will
88 disagree with the change.
89
90 A good mental test is "will the person who hates my work the most be
91 able to find fault with the change" - if so, then it's not obvious and
92 needs to be posted first. :-)
93
94 Something like changing or bypassing an interface is _not_ an obvious
95 fix, since such a change without discussion will result in
96 instantaneous and loud complaints.
97
98 For documentation changes, about the only kind of fix that is obvious
99 is correction of a typo or bad English usage.
100
101
102 GDB Steering Committee
103 ----------------------
104
105 The members of the GDB Steering Committee are the FSF-appointed
106 maintainers of the GDB project.
107
108 The Steering Committee has final authority for all GDB-related topics;
109 they may make whatever changes that they deem necessary, or that the FSF
110 requests. However, they are generally not involved in day-to-day
111 development.
112
113 The current members of the steering committee are listed below, in
114 alphabetical order. Their affiliations are provided for reference only -
115 their membership on the Steering Committee is individual and not through
116 their affiliation, and they act on behalf of the GNU project.
117
118 Jim Blandy (Mozilla)
119 Andrew Cagney (Red Hat)
120 Robert Dewar (AdaCore, NYU)
121 Klee Dienes (Apple)
122 Paul Hilfinger (UC Berkeley)
123 Dan Jacobowitz (CodeSourcery)
124 Stan Shebs (CodeSourcery)
125 Richard Stallman (FSF)
126 Ian Lance Taylor (C2)
127 Todd Whitesel
128
129
130 Global Maintainers
131 ------------------
132
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
137 committing.
138
139 The global maintainers are responsible for reviewing patches to any area
140 for which no Responsible Maintainer is listed.
141
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.
151
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
154 discussion.
155
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.
158
159 The current global maintainers are (in alphabetical order):
160
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 Daniel Jacobowitz dan@debian.org
167 Mark Kettenis kettenis@gnu.org
168 Stan Shebs stan@codesourcery.com
169 Michael Snyder msnyder@vmware.com
170 Tom Tromey tromey@redhat.com
171 Ulrich Weigand Ulrich.Weigand@de.ibm.com
172 Elena Zannoni elena.zannoni@oracle.com
173 Eli Zaretskii eliz@gnu.org
174
175
176 Release Manager
177 ---------------
178
179 The current release manager is: Joel Brobecker <brobecker@adacore.com>
180
181 His responsibilities are:
182
183 * organizing, scheduling, and managing releases of GDB.
184
185 * deciding the approval and commit policies for release branches,
186 and can change them as needed.
187
188
189
190 Patch Champions
191 ---------------
192
193 These volunteers track all patches submitted to the gdb-patches list. They
194 endeavor to prevent any posted patch from being overlooked; work with
195 contributors to meet GDB's coding style and general requirements, along with
196 FSF copyright assignments; remind (ping) responsible maintainers to review
197 patches; and ensure that contributors are given credit.
198
199 Current patch champions (in alphabetical order):
200
201 Randolph Chung <tausq@debian.org>
202
203
204
205 Responsible Maintainers
206 -----------------------
207
208 These developers have agreed to review patches in specific areas of GDB, in
209 which they have knowledge and experience. These areas are generally broad;
210 the role of a responsible maintainer is to provide coherent and cohesive
211 structure within their area of GDB, to assure that patches from many
212 different contributors all work together for the best results.
213
214 Global maintainers will defer to responsible maintainers within their areas,
215 as long as the responsible maintainer is active. Active means that
216 responsible maintainers agree to review submitted patches in their area
217 promptly; patches and followups should generally be answered within a week.
218 If a responsible maintainer is interested in reviewing a patch but will not
219 have time within a week of posting, the maintainer should send an
220 acknowledgement of the patch to the gdb-patches mailing list, and
221 plan to follow up with a review within a month. These deadlines are for
222 initial responses to a patch - if the maintainer has suggestions
223 or questions, it may take an extended discussion before the patch
224 is ready to commit. There are no written requirements for discussion,
225 but maintainers are asked to be responsive.
226
227 If a responsible maintainer misses these deadlines occasionally (e.g.
228 vacation or unexpected workload), it's not a disaster - any global
229 maintainer may step in to review the patch. But sometimes life intervenes
230 more permanently, and a maintainer may no longer have time for these duties.
231 When this happens, he or she should step down (either into the Authorized
232 Committers section if still interested in the area, or simply removed from
233 the list of Responsible Maintainers if not).
234
235 If a responsible maintainer is unresponsive for an extended period of time
236 without stepping down, please contact the Global Maintainers; they will try
237 to contact the maintainer directly and fix the problem - potentially by
238 removing that maintainer from their listed position.
239
240 If there are several maintainers for a given domain then any one of them
241 may review a submitted patch.
242
243 Target Instruction Set Architectures:
244
245 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
246 (Operating System / Application Binary Interface) issues including CPU
247 variants.
248
249 The Target/Architecture maintainer works with the host maintainer when
250 resolving build issues. The Target/Architecture maintainer works with
251 the native maintainer when resolving ABI issues.
252
253 alpha --target=alpha-elf ,-Werror
254
255 arm --target=arm-elf ,-Werror
256 Richard Earnshaw rearnsha@arm.com
257
258 avr --target=avr ,-Werror
259
260 cris --target=cris-elf ,-Werror ,
261 (sim does not build with -Werror)
262
263 frv --target=frv-elf ,-Werror
264
265 h8300 --target=h8300-elf ,-Werror
266
267 i386 --target=i386-elf ,-Werror
268 Mark Kettenis kettenis@gnu.org
269
270 ia64 --target=ia64-linux-gnu ,-Werror
271 (--target=ia64-elf broken)
272
273 m32c --target=m32c-elf ,-Werror
274
275 m32r --target=m32r-elf ,-Werror
276
277 m68hc11 --target=m68hc11-elf ,-Werror ,
278 Stephane Carrez stcarrez@nerim.fr
279
280 m68k --target=m68k-elf ,-Werror
281
282 m88k --target=m88k-openbsd ,-Werror
283 Mark Kettenis kettenis@gnu.org
284
285 mcore Deleted
286
287 mep --target=mep-elf ,-Werror
288 Kevin Buettner kevinb@redhat.com
289
290 mips --target=mips-elf ,-Werror
291
292 mn10300 --target=mn10300-elf broken
293 (sim/ dies with make -j)
294 Michael Snyder msnyder@vmware.com
295
296 moxie --target=moxie-elf ,-Werror
297 Anthony Green green@moxielogic.com
298
299 ms1 --target=ms1-elf ,-Werror
300 Kevin Buettner kevinb@redhat.com
301
302 ns32k Deleted
303
304 pa --target=hppa-elf ,-Werror
305
306 powerpc --target=powerpc-eabi ,-Werror
307
308 s390 --target=s390-linux-gnu ,-Werror
309
310 score --target=score-elf
311 Qinwei qinwei@sunnorth.com.cn
312
313 sh --target=sh-elf ,-Werror
314 --target=sh64-elf ,-Werror
315
316 sparc --target=sparc64-solaris2.10 ,-Werror
317 (--target=sparc-elf broken)
318
319 spu --target=spu-elf ,-Werror
320 Ulrich Weigand uweigand@de.ibm.com
321
322 v850 --target=v850-elf ,-Werror
323
324 vax --target=vax-netbsd ,-Werror
325
326 x86-64 --target=x86_64-linux-gnu ,-Werror
327
328 xstormy16 --target=xstormy16-elf
329 Corinna Vinschen vinschen@redhat.com
330
331 xtensa --target=xtensa-elf
332 Maxim Grigoriev maxim2405@gmail.com
333
334 All developers recognized by this file can make arbitrary changes to
335 OBSOLETE targets.
336
337 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
338 above targets.
339
340
341 Host/Native:
342
343 The Native maintainer is responsible for target specific native
344 support - typically shared libraries and quirks to procfs/ptrace/...
345 The Native maintainer works with the Arch and Core maintainers when
346 resolving more generic problems.
347
348 The host maintainer ensures that gdb can be built as a cross debugger on
349 their platform.
350
351 AIX Joel Brobecker brobecker@adacore.com
352
353 djgpp native Eli Zaretskii eliz@gnu.org
354 GNU Hurd Alfred M. Szmidt ams@gnu.org
355 MS Windows (NT, '00, 9x, Me, XP) host & native
356 Chris Faylor cgf@alum.bu.edu
357 GNU/Linux/x86 native & host
358 Mark Kettenis kettenis@gnu.org
359 GNU/Linux MIPS native & host
360 Daniel Jacobowitz dan@debian.org
361 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
362 FreeBSD native & host Mark Kettenis kettenis@gnu.org
363
364
365
366 Core: Generic components used by all of GDB
367
368 tracing Michael Snyder msnyder@vmware.com
369 threads Michael Snyder msnyder@vmware.com
370 Mark Kettenis kettenis@gnu.org
371 language support
372 Ada Joel Brobecker brobecker@adacore.com
373 Paul Hilfinger hilfinger@gnat.com
374 C++ Daniel Jacobowitz dan@debian.org
375 Objective C support Adam Fedor fedor@gnu.org
376 shared libs Kevin Buettner kevinb@redhat.com
377 MI interface Vladimir Prus vladimir@codesourcery.com
378
379 documentation Eli Zaretskii eliz@gnu.org
380 (including NEWS)
381 testsuite
382 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
383 threads (gdb.threads) Michael Snyder msnyder@vmware.com
384 trace (gdb.trace) Michael Snyder msnyder@vmware.com
385
386
387 UI: External (user) interfaces.
388
389 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
390 Keith Seitz keiths@redhat.com
391 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
392
393
394 Misc:
395
396 gdb/gdbserver Daniel Jacobowitz dan@debian.org
397
398 Makefile.in, configure* ALL
399
400 mmalloc/ ALL Host maintainers
401
402 sim/ See sim/MAINTAINERS
403
404 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
405 ALL
406 Host maintainers (host dependant parts)
407 (but get your changes into the master version)
408
409 tcl/ tk/ itcl/ ALL
410
411
412 Authorized Committers
413 ---------------------
414
415 These are developers working on particular areas of GDB, who are trusted to
416 commit their own (or other developers') patches in those areas without
417 further review from a Global Maintainer or Responsible Maintainer. They are
418 under no obligation to review posted patches - but, of course, are invited
419 to do so!
420
421 PowerPC Andrew Cagney cagney@gnu.org
422 CRIS Hans-Peter Nilsson hp@axis.com
423 IA64 Jeff Johnston jjohnstn@redhat.com
424 MIPS Joel Brobecker brobecker@adacore.com
425 m32r Kei Sakamoto sakamoto.kei@renesas.com
426 PowerPC Kevin Buettner kevinb@redhat.com
427 CRIS Orjan Friberg orjanf@axis.com
428 HPPA Randolph Chung tausq@debian.org
429 S390 Ulrich Weigand uweigand@de.ibm.com
430 djgpp DJ Delorie dj@delorie.com
431 [Please use this address to contact DJ about DJGPP]
432 tui Stephane Carrez stcarrez@nerim.fr
433 ia64 Kevin Buettner kevinb@redhat.com
434 AIX Kevin Buettner kevinb@redhat.com
435 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
436 gdb.java tests Anthony Green green@redhat.com
437 FreeBSD native & host David O'Brien obrien@freebsd.org
438 event loop Elena Zannoni elena.zannoni@oracle.com
439 generic symtabs Elena Zannoni elena.zannoni@oracle.com
440 dwarf readers Elena Zannoni elena.zannoni@oracle.com
441 elf reader Elena Zannoni elena.zannoni@oracle.com
442 stabs reader Elena Zannoni elena.zannoni@oracle.com
443 readline/ Elena Zannoni elena.zannoni@oracle.com
444 NetBSD native & host Jason Thorpe thorpej@netbsd.org
445 Pascal support Pierre Muller muller@sources.redhat.com
446 avr Theodore A. Roth troth@openavr.org
447 Modula-2 support Gaius Mulley gaius@glam.ac.uk
448
449
450 Write After Approval
451 (alphabetic)
452
453 To get recommended for the Write After Approval list you need a valid
454 FSF assignment and have submitted one good patch.
455
456 Pedro Alves pedro_alves@portugalmail.pt
457 David Anderson davea@sgi.com
458 John David Anglin dave.anglin@nrc-cnrc.gc.ca
459 Shrinivas Atre shrinivasa@kpitcummins.com
460 Scott Bambrough scottb@netwinder.org
461 Thiago Jung Bauermann bauerman@br.ibm.com
462 Jan Beulich jbeulich@novell.com
463 Jim Blandy jimb@codesourcery.com
464 Philip Blundell philb@gnu.org
465 Per Bothner per@bothner.com
466 Joel Brobecker brobecker@adacore.com
467 Dave Brolley brolley@redhat.com
468 Paul Brook paul@codesourcery.com
469 Julian Brown julian@codesourcery.com
470 Kevin Buettner kevinb@redhat.com
471 Andrew Cagney cagney@gnu.org
472 David Carlton carlton@bactrian.org
473 Stephane Carrez stcarrez@nerim.fr
474 Michael Chastain mec.gnu@mindspring.com
475 Eric Christopher echristo@apple.com
476 Randolph Chung tausq@debian.org
477 Nick Clifton nickc@redhat.com
478 J.T. Conklin jtc@acorntoolworks.com
479 Brendan Conoboy blc@redhat.com
480 Ludovic Courtès ludo@gnu.org
481 DJ Delorie dj@redhat.com
482 Chris Demetriou cgd@google.com
483 Philippe De Muyter phdm@macqel.be
484 Dhananjay Deshpande dhananjayd@kpitcummins.com
485 Markus Deuling deuling@de.ibm.com
486 Klee Dienes kdienes@apple.com
487 Gabriel Dos Reis gdr@integrable-solutions.net
488 Richard Earnshaw rearnsha@arm.com
489 Steve Ellcey sje@cup.hp.com
490 Frank Ch. Eigler fche@redhat.com
491 Ben Elliston bje@gnu.org
492 Doug Evans dje@google.com
493 Adam Fedor fedor@gnu.org
494 Brian Ford ford@vss.fsi.com
495 Orjan Friberg orjanf@axis.com
496 Nathan Froyd froydnj@codesourcery.com
497 Gary Funck gary@intrepid.com
498 Paul Gilliam pgilliam@us.ibm.com
499 Tristan Gingold gingold@adacore.com
500 Raoul Gough RaoulGough@yahoo.co.uk
501 Anthony Green green@redhat.com
502 Matthew Green mrg@eterna.com.au
503 Maxim Grigoriev maxim2405@gmail.com
504 Jerome Guitton guitton@act-europe.fr
505 Ben Harris bjh21@netbsd.org
506 Richard Henderson rth@redhat.com
507 Aldy Hernandez aldyh@redhat.com
508 Paul Hilfinger hilfinger@gnat.com
509 Matt Hiller hiller@redhat.com
510 Kazu Hirata kazu@cs.umass.edu
511 Jeff Holcomb jeffh@redhat.com
512 Don Howard dhoward@redhat.com
513 Nick Hudson nick.hudson@dsl.pipex.com
514 Martin Hunt hunt@redhat.com
515 Jim Ingham jingham@apple.com
516 Baurzhan Ismagulov ibr@radix50.net
517 Manoj Iyer manjo@austin.ibm.com
518 Daniel Jacobowitz dan@debian.org
519 Andreas Jaeger aj@suse.de
520 Jeff Johnston jjohnstn@redhat.com
521 Geoff Keating geoffk@redhat.com
522 Mark Kettenis kettenis@gnu.org
523 Marc Khouzam marc.khouzam@ericsson.com
524 Jim Kingdon kingdon@panix.com
525 Jan Kratochvil jan.kratochvil@redhat.com
526 Jonathan Larmour jifl@ecoscentric.com
527 Jeff Law law@redhat.com
528 David Lecomber david@streamline-computing.com
529 Robert Lipe rjl@sco.com
530 Sandra Loosemore sandra@codesourcery.com
531 H.J. Lu hjl.tools@gmail.com
532 Michal Ludvig mludvig@suse.cz
533 Luis Machado luisgpm@br.ibm.com
534 Glen McCready gkm@redhat.com
535 Greg McGary greg@mcgary.org
536 Roland McGrath roland@redhat.com
537 Bryce McKinlay mckinlay@redhat.com
538 Jason Merrill jason@redhat.com
539 David S. Miller davem@redhat.com
540 Mark Mitchell mark@codesourcery.com
541 Marko Mlinar markom@opencores.org
542 Alan Modra amodra@bigpond.net.au
543 Jason Molenda jmolenda@apple.com
544 Phil Muldoon pmuldoon@redhat.com
545 Pierre Muller muller@sources.redhat.com
546 Gaius Mulley gaius@glam.ac.uk
547 Joseph Myers joseph@codesourcery.com
548 Fernando Nasser fnasser@redhat.com
549 Adam Nemet anemet@caviumnetworks.com
550 Nathanael Nerode neroden@gcc.gnu.org
551 Hans-Peter Nilsson hp@bitrange.com
552 David O'Brien obrien@freebsd.org
553 Alexandre Oliva aoliva@redhat.com
554 Denis Pilat denis.pilat@st.com
555 Vladimir Prus vladimir@codesourcery.com
556 Qinwei qinwei@sunnorth.com.cn
557 Frederic Riss frederic.riss@st.com
558 Aleksandar Ristovski aristovski@qnx.com
559 Tom Rix trix@redhat.com
560 Nick Roberts nickrob@snap.net.nz
561 Bob Rossi bob_rossi@cox.net
562 Theodore A. Roth troth@openavr.org
563 Ian Roxborough irox@redhat.com
564 Maciej W. Rozycki macro@linux-mips.org
565 Grace Sainsbury graces@redhat.com
566 Kei Sakamoto sakamoto.kei@renesas.com
567 Mark Salter msalter@redhat.com
568 Richard Sandiford richard@codesourcery.com
569 Peter Schauer Peter.Schauer@mytum.de
570 Andreas Schwab schwab@linux-m68k.org
571 Thomas Schwinge tschwinge@gnu.org
572 Keith Seitz keiths@redhat.com
573 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
574 Stan Shebs stan@codesourcery.com
575 Joel Sherrill joel.sherrill@oarcorp.com
576 Mark Shinwell shinwell@codesourcery.com
577 Craig Silverstein csilvers@google.com
578 Aidan Skinner aidan@velvet.net
579 Jiri Smid smid@suse.cz
580 David Smith dsmith@redhat.com
581 Stephen P. Smith ischis2@cox.net
582 Jackie Smith Cashion jsmith@redhat.com
583 Michael Snyder msnyder@vmware.com
584 Petr Sorfa petrs@caldera.com
585 Andrew Stubbs ams@codesourcery.com
586 Emi Suzuki emi-suzuki@tjsys.co.jp
587 Ian Lance Taylor ian@airs.com
588 Gary Thomas gthomas@redhat.com
589 Jason Thorpe thorpej@netbsd.org
590 Caroline Tice ctice@apple.com
591 Kai Tietz kai.tietz@onevision.com
592 Tom Tromey tromey@redhat.com
593 David Ung davidu@mips.com
594 D Venkatasubramanian dvenkat@noida.hcltech.com
595 Corinna Vinschen vinschen@redhat.com
596 Keith Walker keith.walker@arm.com
597 Kris Warkentin kewarken@qnx.com
598 Ulrich Weigand uweigand@de.ibm.com
599 Nathan Williams nathanw@wasabisystems.com
600 Bob Wilson bob.wilson@acm.org
601 Jim Wilson wilson@tuliptree.org
602 Elena Zannoni elena.zannoni@oracle.com
603 Eli Zaretskii eliz@gnu.org
604 Wu Zhou woodzltc@cn.ibm.com
605 Yoshinori Sato ysato@users.sourceforge.jp
606 Hui Zhu teawater@gmail.com
607 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
608
609
610 Past Maintainers
611
612 Whenever removing yourself, or someone else, from this file, consider
613 listing their areas of development here for posterity.
614
615 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
616 Jeff Law (hppa) law at cygnus dot com
617 Daniel Berlin (C++ support) dan at cgsoftware dot com
618 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
619 David Taylor (d10v, sparc, utils, defs,
620 expression evaluator, language support) taylor at candd dot org
621 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
622 Frank Ch. Eigler (sim) fche at redhat dot com
623 Per Bothner (Java) per at bothner dot com
624 Anthony Green (Java) green at redhat dot com
625 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
626 Mark Salter (testsuite/lib+config) msalter at redhat dot com
627 Jim Kingdon (web pages) kingdon at panix dot com
628 Jim Ingham (gdbtk, libgui) jingham at apple dot com
629 Mark Kettenis (hurd native) kettenis at gnu dot org
630 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
631 Robert Lipe (SCO/Unixware) rjl at sco dot com
632 Peter Schauer (global, AIX, xcoffsolib,
633 Solaris/x86) Peter.Schauer at mytum dot de
634 Scott Bambrough (ARM) scottb at netwinder dot org
635 Philippe De Muyter (coff) phdm at macqel dot be
636 Michael Chastain (testsuite) mec.gnu at mindspring dot com
637 Fred Fish (global)
638
639
640
641 Folks that have been caught up in a paper trail:
642
643 David Carlton carlton@bactrian.org
644 Ramana Radhakrishnan ramana.r@gmail.com
645
646 ;; Local Variables:
647 ;; coding: utf-8
648 ;; End: