gdb/
[deliverable/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 lm32 --target=lm32-elf ,-Werror
274
275 m32c --target=m32c-elf ,-Werror
276
277 m32r --target=m32r-elf ,-Werror
278
279 m68hc11 --target=m68hc11-elf ,-Werror ,
280 Stephane Carrez stcarrez@nerim.fr
281
282 m68k --target=m68k-elf ,-Werror
283
284 m88k --target=m88k-openbsd ,-Werror
285 Mark Kettenis kettenis@gnu.org
286
287 mcore Deleted
288
289 mep --target=mep-elf ,-Werror
290 Kevin Buettner kevinb@redhat.com
291
292 mips --target=mips-elf ,-Werror
293
294 mn10300 --target=mn10300-elf broken
295 (sim/ dies with make -j)
296 Michael Snyder msnyder@vmware.com
297
298 moxie --target=moxie-elf ,-Werror
299 Anthony Green green@moxielogic.com
300
301 ms1 --target=ms1-elf ,-Werror
302 Kevin Buettner kevinb@redhat.com
303
304 ns32k Deleted
305
306 pa --target=hppa-elf ,-Werror
307
308 powerpc --target=powerpc-eabi ,-Werror
309
310 s390 --target=s390-linux-gnu ,-Werror
311
312 score --target=score-elf
313 Qinwei qinwei@sunnorth.com.cn
314
315 sh --target=sh-elf ,-Werror
316 --target=sh64-elf ,-Werror
317
318 sparc --target=sparc64-solaris2.10 ,-Werror
319 (--target=sparc-elf broken)
320
321 spu --target=spu-elf ,-Werror
322 Ulrich Weigand uweigand@de.ibm.com
323
324 v850 --target=v850-elf ,-Werror
325
326 vax --target=vax-netbsd ,-Werror
327
328 x86-64 --target=x86_64-linux-gnu ,-Werror
329
330 xstormy16 --target=xstormy16-elf
331 Corinna Vinschen vinschen@redhat.com
332
333 xtensa --target=xtensa-elf
334 Maxim Grigoriev maxim2405@gmail.com
335
336 All developers recognized by this file can make arbitrary changes to
337 OBSOLETE targets.
338
339 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
340 above targets.
341
342
343 Host/Native:
344
345 The Native maintainer is responsible for target specific native
346 support - typically shared libraries and quirks to procfs/ptrace/...
347 The Native maintainer works with the Arch and Core maintainers when
348 resolving more generic problems.
349
350 The host maintainer ensures that gdb can be built as a cross debugger on
351 their platform.
352
353 AIX Joel Brobecker brobecker@adacore.com
354
355 djgpp native Eli Zaretskii eliz@gnu.org
356 GNU Hurd Alfred M. Szmidt ams@gnu.org
357 MS Windows (NT, '00, 9x, Me, XP) host & native
358 Chris Faylor cgf@alum.bu.edu
359 GNU/Linux/x86 native & host
360 Mark Kettenis kettenis@gnu.org
361 GNU/Linux MIPS native & host
362 Daniel Jacobowitz dan@debian.org
363 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
364 FreeBSD native & host Mark Kettenis kettenis@gnu.org
365
366
367
368 Core: Generic components used by all of GDB
369
370 tracing Michael Snyder msnyder@vmware.com
371 threads Michael Snyder msnyder@vmware.com
372 Mark Kettenis kettenis@gnu.org
373 language support
374 Ada Joel Brobecker brobecker@adacore.com
375 Paul Hilfinger hilfinger@gnat.com
376 C++ Daniel Jacobowitz dan@debian.org
377 Objective C support Adam Fedor fedor@gnu.org
378 shared libs Kevin Buettner kevinb@redhat.com
379 MI interface Vladimir Prus vladimir@codesourcery.com
380
381 documentation Eli Zaretskii eliz@gnu.org
382 (including NEWS)
383 testsuite
384 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
385 threads (gdb.threads) Michael Snyder msnyder@vmware.com
386 trace (gdb.trace) Michael Snyder msnyder@vmware.com
387
388
389 UI: External (user) interfaces.
390
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
394
395
396 Misc:
397
398 gdb/gdbserver Daniel Jacobowitz dan@debian.org
399
400 Makefile.in, configure* ALL
401
402 mmalloc/ ALL Host maintainers
403
404 sim/ See sim/MAINTAINERS
405
406 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
407 ALL
408 Host maintainers (host dependant parts)
409 (but get your changes into the master version)
410
411 tcl/ tk/ itcl/ ALL
412
413
414 Authorized Committers
415 ---------------------
416
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
421 to do so!
422
423 PowerPC Andrew Cagney cagney@gnu.org
424 CRIS Hans-Peter Nilsson hp@axis.com
425 IA64 Jeff Johnston jjohnstn@redhat.com
426 MIPS Joel Brobecker brobecker@adacore.com
427 m32r Kei Sakamoto sakamoto.kei@renesas.com
428 PowerPC Kevin Buettner kevinb@redhat.com
429 CRIS Orjan Friberg orjanf@axis.com
430 HPPA Randolph Chung tausq@debian.org
431 S390 Ulrich Weigand uweigand@de.ibm.com
432 djgpp DJ Delorie dj@delorie.com
433 [Please use this address to contact DJ about DJGPP]
434 tui Stephane Carrez stcarrez@nerim.fr
435 ia64 Kevin Buettner kevinb@redhat.com
436 AIX Kevin Buettner kevinb@redhat.com
437 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
438 gdb.java tests Anthony Green green@redhat.com
439 FreeBSD native & host David O'Brien obrien@freebsd.org
440 event loop Elena Zannoni elena.zannoni@oracle.com
441 generic symtabs Elena Zannoni elena.zannoni@oracle.com
442 dwarf readers Elena Zannoni elena.zannoni@oracle.com
443 elf reader Elena Zannoni elena.zannoni@oracle.com
444 stabs reader Elena Zannoni elena.zannoni@oracle.com
445 readline/ Elena Zannoni elena.zannoni@oracle.com
446 NetBSD native & host Jason Thorpe thorpej@netbsd.org
447 Pascal support Pierre Muller muller@sourceware.org
448 avr Theodore A. Roth troth@openavr.org
449 Modula-2 support Gaius Mulley gaius@glam.ac.uk
450
451
452 Write After Approval
453 (alphabetic)
454
455 To get recommended for the Write After Approval list you need a valid
456 FSF assignment and have submitted one good patch.
457
458 Pedro Alves pedro_alves@portugalmail.pt
459 David Anderson davea@sgi.com
460 John David Anglin dave.anglin@nrc-cnrc.gc.ca
461 Shrinivas Atre shrinivasa@kpitcummins.com
462 Scott Bambrough scottb@netwinder.org
463 Thiago Jung Bauermann bauerman@br.ibm.com
464 Jon Beniston jon@beniston.com
465 Jan Beulich jbeulich@novell.com
466 Jim Blandy jimb@codesourcery.com
467 Philip Blundell philb@gnu.org
468 Per Bothner per@bothner.com
469 Joel Brobecker brobecker@adacore.com
470 Dave Brolley brolley@redhat.com
471 Paul Brook paul@codesourcery.com
472 Julian Brown julian@codesourcery.com
473 Kevin Buettner kevinb@redhat.com
474 Andrew Cagney cagney@gnu.org
475 David Carlton carlton@bactrian.org
476 Stephane Carrez stcarrez@nerim.fr
477 Michael Chastain mec.gnu@mindspring.com
478 Eric Christopher echristo@apple.com
479 Randolph Chung tausq@debian.org
480 Nick Clifton nickc@redhat.com
481 J.T. Conklin jtc@acorntoolworks.com
482 Brendan Conoboy blc@redhat.com
483 Ludovic Courtès ludo@gnu.org
484 DJ Delorie dj@redhat.com
485 Chris Demetriou cgd@google.com
486 Philippe De Muyter phdm@macqel.be
487 Dhananjay Deshpande dhananjayd@kpitcummins.com
488 Markus Deuling deuling@de.ibm.com
489 Klee Dienes kdienes@apple.com
490 Gabriel Dos Reis gdr@integrable-solutions.net
491 Richard Earnshaw rearnsha@arm.com
492 Steve Ellcey sje@cup.hp.com
493 Frank Ch. Eigler fche@redhat.com
494 Ben Elliston bje@gnu.org
495 Doug Evans dje@google.com
496 Adam Fedor fedor@gnu.org
497 Brian Ford ford@vss.fsi.com
498 Orjan Friberg orjanf@axis.com
499 Nathan Froyd froydnj@codesourcery.com
500 Gary Funck gary@intrepid.com
501 Paul Gilliam pgilliam@us.ibm.com
502 Tristan Gingold gingold@adacore.com
503 Raoul Gough RaoulGough@yahoo.co.uk
504 Anthony Green green@redhat.com
505 Matthew Green mrg@eterna.com.au
506 Maxim Grigoriev maxim2405@gmail.com
507 Jerome Guitton guitton@act-europe.fr
508 Ben Harris bjh21@netbsd.org
509 Richard Henderson rth@redhat.com
510 Aldy Hernandez aldyh@redhat.com
511 Paul Hilfinger hilfinger@gnat.com
512 Matt Hiller hiller@redhat.com
513 Kazu Hirata kazu@cs.umass.edu
514 Jeff Holcomb jeffh@redhat.com
515 Don Howard dhoward@redhat.com
516 Nick Hudson nick.hudson@dsl.pipex.com
517 Martin Hunt hunt@redhat.com
518 Jim Ingham jingham@apple.com
519 Baurzhan Ismagulov ibr@radix50.net
520 Manoj Iyer manjo@austin.ibm.com
521 Daniel Jacobowitz dan@debian.org
522 Andreas Jaeger aj@suse.de
523 Jeff Johnston jjohnstn@redhat.com
524 Geoff Keating geoffk@redhat.com
525 Mark Kettenis kettenis@gnu.org
526 Marc Khouzam marc.khouzam@ericsson.com
527 Jim Kingdon kingdon@panix.com
528 Jan Kratochvil jan.kratochvil@redhat.com
529 Jonathan Larmour jifl@ecoscentric.com
530 Jeff Law law@redhat.com
531 David Lecomber david@streamline-computing.com
532 Robert Lipe rjl@sco.com
533 Sandra Loosemore sandra@codesourcery.com
534 H.J. Lu hjl.tools@gmail.com
535 Michal Ludvig mludvig@suse.cz
536 Luis Machado luisgpm@br.ibm.com
537 Glen McCready gkm@redhat.com
538 Greg McGary greg@mcgary.org
539 Roland McGrath roland@redhat.com
540 Bryce McKinlay mckinlay@redhat.com
541 Jason Merrill jason@redhat.com
542 David S. Miller davem@redhat.com
543 Mark Mitchell mark@codesourcery.com
544 Marko Mlinar markom@opencores.org
545 Alan Modra amodra@bigpond.net.au
546 Jason Molenda jmolenda@apple.com
547 Phil Muldoon pmuldoon@redhat.com
548 Pierre Muller muller@sourceware.org
549 Gaius Mulley gaius@glam.ac.uk
550 Joseph Myers joseph@codesourcery.com
551 Fernando Nasser fnasser@redhat.com
552 Adam Nemet anemet@caviumnetworks.com
553 Nathanael Nerode neroden@gcc.gnu.org
554 Hans-Peter Nilsson hp@bitrange.com
555 David O'Brien obrien@freebsd.org
556 Alexandre Oliva aoliva@redhat.com
557 Karen Osmond karen.osmond@gmail.com
558 Denis Pilat denis.pilat@st.com
559 Vladimir Prus vladimir@codesourcery.com
560 Qinwei qinwei@sunnorth.com.cn
561 Frederic Riss frederic.riss@st.com
562 Aleksandar Ristovski aristovski@qnx.com
563 Tom Rix trix@redhat.com
564 Nick Roberts nickrob@snap.net.nz
565 Bob Rossi bob_rossi@cox.net
566 Theodore A. Roth troth@openavr.org
567 Ian Roxborough irox@redhat.com
568 Maciej W. Rozycki macro@linux-mips.org
569 Grace Sainsbury graces@redhat.com
570 Kei Sakamoto sakamoto.kei@renesas.com
571 Mark Salter msalter@redhat.com
572 Richard Sandiford richard@codesourcery.com
573 Peter Schauer Peter.Schauer@mytum.de
574 Andreas Schwab schwab@linux-m68k.org
575 Thomas Schwinge tschwinge@gnu.org
576 Keith Seitz keiths@redhat.com
577 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
578 Stan Shebs stan@codesourcery.com
579 Joel Sherrill joel.sherrill@oarcorp.com
580 Mark Shinwell shinwell@codesourcery.com
581 Craig Silverstein csilvers@google.com
582 Aidan Skinner aidan@velvet.net
583 Jiri Smid smid@suse.cz
584 David Smith dsmith@redhat.com
585 Stephen P. Smith ischis2@cox.net
586 Jackie Smith Cashion jsmith@redhat.com
587 Michael Snyder msnyder@vmware.com
588 Petr Sorfa petrs@caldera.com
589 Andrew Stubbs ams@codesourcery.com
590 Emi Suzuki emi-suzuki@tjsys.co.jp
591 Ian Lance Taylor ian@airs.com
592 Gary Thomas gthomas@redhat.com
593 Jason Thorpe thorpej@netbsd.org
594 Caroline Tice ctice@apple.com
595 Kai Tietz kai.tietz@onevision.com
596 Tom Tromey tromey@redhat.com
597 David Ung davidu@mips.com
598 D Venkatasubramanian dvenkat@noida.hcltech.com
599 Corinna Vinschen vinschen@redhat.com
600 Sami Wagiaalla swagiaal@redhat.com
601 Keith Walker keith.walker@arm.com
602 Kris Warkentin kewarken@qnx.com
603 Ulrich Weigand uweigand@de.ibm.com
604 Nathan Williams nathanw@wasabisystems.com
605 Bob Wilson bob.wilson@acm.org
606 Jim Wilson wilson@tuliptree.org
607 Elena Zannoni elena.zannoni@oracle.com
608 Eli Zaretskii eliz@gnu.org
609 Wu Zhou woodzltc@cn.ibm.com
610 Yoshinori Sato ysato@users.sourceforge.jp
611 Hui Zhu teawater@gmail.com
612 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
613
614
615 Past Maintainers
616
617 Whenever removing yourself, or someone else, from this file, consider
618 listing their areas of development here for posterity.
619
620 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
621 Jeff Law (hppa) law at cygnus dot com
622 Daniel Berlin (C++ support) dan at cgsoftware dot com
623 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
624 David Taylor (d10v, sparc, utils, defs,
625 expression evaluator, language support) taylor at candd dot org
626 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
627 Frank Ch. Eigler (sim) fche at redhat dot com
628 Per Bothner (Java) per at bothner dot com
629 Anthony Green (Java) green at redhat dot com
630 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
631 Mark Salter (testsuite/lib+config) msalter at redhat dot com
632 Jim Kingdon (web pages) kingdon at panix dot com
633 Jim Ingham (gdbtk, libgui) jingham at apple dot com
634 Mark Kettenis (hurd native) kettenis at gnu dot org
635 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
636 Robert Lipe (SCO/Unixware) rjl at sco dot com
637 Peter Schauer (global, AIX, xcoffsolib,
638 Solaris/x86) Peter.Schauer at mytum dot de
639 Scott Bambrough (ARM) scottb at netwinder dot org
640 Philippe De Muyter (coff) phdm at macqel dot be
641 Michael Chastain (testsuite) mec.gnu at mindspring dot com
642 Fred Fish (global)
643
644
645
646 Folks that have been caught up in a paper trail:
647
648 David Carlton carlton@bactrian.org
649 Ramana Radhakrishnan ramana.r@gmail.com
650
651 ;; Local Variables:
652 ;; coding: utf-8
653 ;; End:
This page took 0.057498 seconds and 5 git commands to generate.