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