projects / binutils-gdb.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
history | raw | HEAD
2012-11-07 Pedro Alves <palves@redhat.com>
[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 Official FSF-appointed GDB Maintainers.
59
60 These maintainers are the ones who take the overall responsibility
61 for GDB, as a package of the GNU project. Other GDB contributors
62 work under the official maintainers' supervision. They have final
63 and overriding authority for all GDB-related decisions, including
64 anything described in this file. As individuals, they may or not
65 be generally involved in day-to-day development.
66
67 - The Release Manager.
68
69 This developer is in charge of making new releases of GDB.
70
71 - The Patch Champions.
72
73 These volunteers make sure that no contribution is overlooked or
74 forgotten.
75
76 Most changes to the list of maintainers in this file are handled by
77 consensus among the global maintainers and any other involved parties.
78 In cases where consensus can not be reached, the global maintainers may
79 ask the official FSF-appointed GDB maintainers for a final decision.
80
81
82 The Obvious Fix Rule
83 --------------------
84
85 All maintainers listed in this file, including the Write After Approval
86 developers, are allowed to check in obvious fixes.
87
88 An "obvious fix" means that there is no possibility that anyone will
89 disagree with the change.
90
91 A good mental test is "will the person who hates my work the most be
92 able to find fault with the change" - if so, then it's not obvious and
93 needs to be posted first. :-)
94
95 Something like changing or bypassing an interface is _not_ an obvious
96 fix, since such a change without discussion will result in
97 instantaneous and loud complaints.
98
99 For documentation changes, about the only kind of fix that is obvious
100 is correction of a typo or bad English usage.
101
102
103 The Official FSF-appointed GDB Maintainers
104 ------------------------------------------
105
106 These maintainers as a group have final authority for all GDB-related
107 topics; they may make whatever changes that they deem necessary, or
108 that the FSF requests.
109
110 The current official FSF-appointed GDB maintainers are listed below,
111 in alphabetical order. Their affiliations are provided for reference
112 only - their maintainership status is individual and not through their
113 affiliation, and they act on behalf of the GNU project.
114
115 Pedro Alves (Red Hat)
116 Joel Brobecker (AdaCore)
117 Doug Evans (Google)
118 Jan Kratochvil (Red Hat)
119 Tom Tromey (Red Hat)
120 Eli Zaretskii
121
122 Global Maintainers
123 ------------------
124
125 The global maintainers may review and commit any change to GDB, except in
126 areas with a Responsible Maintainer available. For major changes, or
127 changes to areas with other active developers, global maintainers are
128 strongly encouraged to post their own patches for feedback before
129 committing.
130
131 The global maintainers are responsible for reviewing patches to any area
132 for which no Responsible Maintainer is listed.
133
134 Global maintainers also have the authority to revert patches which should
135 not have been applied, e.g. patches which were not approved, controversial
136 patches committed under the Obvious Fix Rule, patches with important bugs
137 that can't be immediately fixed, or patches which go against an accepted and
138 documented roadmap for GDB development. Any global maintainer may request
139 the reversion of a patch. If no global maintainer, or responsible
140 maintainer in the affected areas, supports the patch (except for the
141 maintainer who originally committed it), then after 48 hours the maintainer
142 who called for the reversion may revert the patch.
143
144 No one may reapply a reverted patch without the agreement of the maintainer
145 who reverted it, or bringing the issue to the official FSF-appointed
146 GDB maintainers for discussion.
147
148 At the moment there are no documented roadmaps for GDB development; in the
149 future, if there are, a reference to the list will be included here.
150
151 The current global maintainers are (in alphabetical order):
152
153 Pedro Alves palves@redhat.com
154 Joel Brobecker brobecker@adacore.com
155 Kevin Buettner kevinb@redhat.com
156 Andrew Cagney cagney@gnu.org
157 Doug Evans dje@google.com
158 Daniel Jacobowitz drow@false.org
159 Mark Kettenis kettenis@gnu.org
160 Jan Kratochvil jan.kratochvil@redhat.com
161 Stan Shebs stan@codesourcery.com
162 Tom Tromey tromey@redhat.com
163 Ulrich Weigand Ulrich.Weigand@de.ibm.com
164 Elena Zannoni elena.zannoni@oracle.com
165 Eli Zaretskii eliz@gnu.org
166
167
168 Release Manager
169 ---------------
170
171 The current release manager is: Joel Brobecker <brobecker@adacore.com>
172
173 His responsibilities are:
174
175 * organizing, scheduling, and managing releases of GDB.
176
177 * deciding the approval and commit policies for release branches,
178 and can change them as needed.
179
180
181
182 Patch Champions
183 ---------------
184
185 These volunteers track all patches submitted to the gdb-patches list. They
186 endeavor to prevent any posted patch from being overlooked; work with
187 contributors to meet GDB's coding style and general requirements, along with
188 FSF copyright assignments; remind (ping) responsible maintainers to review
189 patches; and ensure that contributors are given credit.
190
191 Current patch champions (in alphabetical order):
192
193 Randolph Chung <tausq@debian.org>
194
195
196
197 Responsible Maintainers
198 -----------------------
199
200 These developers have agreed to review patches in specific areas of GDB, in
201 which they have knowledge and experience. These areas are generally broad;
202 the role of a responsible maintainer is to provide coherent and cohesive
203 structure within their area of GDB, to assure that patches from many
204 different contributors all work together for the best results.
205
206 Global maintainers will defer to responsible maintainers within their areas,
207 as long as the responsible maintainer is active. Active means that
208 responsible maintainers agree to review submitted patches in their area
209 promptly; patches and followups should generally be answered within a week.
210 If a responsible maintainer is interested in reviewing a patch but will not
211 have time within a week of posting, the maintainer should send an
212 acknowledgement of the patch to the gdb-patches mailing list, and
213 plan to follow up with a review within a month. These deadlines are for
214 initial responses to a patch - if the maintainer has suggestions
215 or questions, it may take an extended discussion before the patch
216 is ready to commit. There are no written requirements for discussion,
217 but maintainers are asked to be responsive.
218
219 If a responsible maintainer misses these deadlines occasionally (e.g.
220 vacation or unexpected workload), it's not a disaster - any global
221 maintainer may step in to review the patch. But sometimes life intervenes
222 more permanently, and a maintainer may no longer have time for these duties.
223 When this happens, he or she should step down (either into the Authorized
224 Committers section if still interested in the area, or simply removed from
225 the list of Responsible Maintainers if not).
226
227 If a responsible maintainer is unresponsive for an extended period of time
228 without stepping down, please contact the Global Maintainers; they will try
229 to contact the maintainer directly and fix the problem - potentially by
230 removing that maintainer from their listed position.
231
232 If there are several maintainers for a given domain then any one of them
233 may review a submitted patch.
234
235 Target Instruction Set Architectures:
236
237 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
238 (Operating System / Application Binary Interface) issues including CPU
239 variants.
240
241 The Target/Architecture maintainer works with the host maintainer when
242 resolving build issues. The Target/Architecture maintainer works with
243 the native maintainer when resolving ABI issues.
244
245 alpha --target=alpha-elf ,-Werror
246
247 arm --target=arm-elf ,-Werror
248
249 avr --target=avr ,-Werror
250 Tristan Gingold gingold@adacore.com
251
252 cris --target=cris-elf ,-Werror ,
253 (sim does not build with -Werror)
254
255 frv --target=frv-elf ,-Werror
256
257 h8300 --target=h8300-elf ,-Werror
258
259 i386 --target=i386-elf ,-Werror
260 Mark Kettenis kettenis@gnu.org
261
262 ia64 --target=ia64-linux-gnu ,-Werror
263 (--target=ia64-elf broken)
264
265 lm32 --target=lm32-elf ,-Werror
266
267 m32c --target=m32c-elf ,-Werror
268
269 m32r --target=m32r-elf ,-Werror
270
271 m68hc11 --target=m68hc11-elf ,-Werror ,
272 Stephane Carrez Stephane.Carrez@gmail.com
273
274 m68k --target=m68k-elf ,-Werror
275
276 m88k --target=m88k-openbsd ,-Werror
277 Mark Kettenis kettenis@gnu.org
278
279 mcore Deleted
280
281 mep --target=mep-elf ,-Werror
282 Kevin Buettner kevinb@redhat.com
283
284 microblaze --target=microblaze-xilinx-elf ,-Werror
285 --target=microblaze-linux-gnu ,-Werror
286 Michael Eager eager@eagercon.com
287
288 mips --target=mips-elf ,-Werror
289 Maciej W. Rozycki macro@codesourcery.com
290
291 mn10300 --target=mn10300-elf broken
292 (sim/ dies with make -j)
293
294 moxie --target=moxie-elf ,-Werror
295 Anthony Green green@moxielogic.com
296
297 ms1 --target=ms1-elf ,-Werror
298 Kevin Buettner kevinb@redhat.com
299
300 ns32k Deleted
301
302 pa --target=hppa-elf ,-Werror
303
304 powerpc --target=powerpc-eabi ,-Werror
305
306 rl78 --target=rl78-elf ,-Werror
307
308 rx --target=rx-elf ,-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 tic6x --target=tic6x-elf ,-Werror
325 Yao Qi yao@codesourcery.com
326
327 v850 --target=v850-elf ,-Werror
328
329 vax --target=vax-netbsd ,-Werror
330
331 x86-64 --target=x86_64-linux-gnu ,-Werror
332
333 xstormy16 --target=xstormy16-elf
334 Corinna Vinschen vinschen@redhat.com
335
336 xtensa --target=xtensa-elf
337 Maxim Grigoriev maxim2405@gmail.com
338
339 All developers recognized by this file can make arbitrary changes to
340 OBSOLETE targets.
341
342 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
343 above targets.
344
345
346 Host/Native:
347
348 The Native maintainer is responsible for target specific native
349 support - typically shared libraries and quirks to procfs/ptrace/...
350 The Native maintainer works with the Arch and Core maintainers when
351 resolving more generic problems.
352
353 The host maintainer ensures that gdb can be built as a cross debugger on
354 their platform.
355
356 AIX Joel Brobecker brobecker@adacore.com
357 Darwin Tristan Gingold gingold@adacore.com
358 djgpp native Eli Zaretskii eliz@gnu.org
359 GNU Hurd Alfred M. Szmidt ams@gnu.org
360 GNU/Linux/x86 native & host
361 Mark Kettenis kettenis@gnu.org
362 GNU/Linux MIPS native & host
363 Daniel Jacobowitz drow@false.org
364 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
365 FreeBSD native & host Mark Kettenis kettenis@gnu.org
366
367
368
369 Core: Generic components used by all of GDB
370
371 threads Mark Kettenis kettenis@gnu.org
372
373 language support
374 Ada Joel Brobecker brobecker@adacore.com
375 Paul Hilfinger hilfinger@gnat.com
376 C++ Daniel Jacobowitz drow@false.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
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 drow@false.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 ARM Richard Earnshaw rearnsha@arm.com
423 CRIS Hans-Peter Nilsson hp@axis.com
424 IA64 Jeff Johnston jjohnstn@redhat.com
425 MIPS Joel Brobecker brobecker@adacore.com
426 m32r Kei Sakamoto sakamoto.kei@renesas.com
427 PowerPC Kevin Buettner kevinb@redhat.com
428 CRIS Orjan Friberg orjanf@axis.com
429 HPPA Randolph Chung tausq@debian.org
430 S390 Ulrich Weigand uweigand@de.ibm.com
431 djgpp DJ Delorie dj@delorie.com
432 [Please use this address to contact DJ about DJGPP]
433 tui Stephane Carrez Stephane.Carrez@gmail.com
434 ia64 Kevin Buettner kevinb@redhat.com
435 AIX Kevin Buettner kevinb@redhat.com
436 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
437 gdb.java tests Anthony Green green@redhat.com
438 FreeBSD native & host David O'Brien obrien@freebsd.org
439 event loop Elena Zannoni elena.zannoni@oracle.com
440 generic symtabs Elena Zannoni elena.zannoni@oracle.com
441 dwarf readers Elena Zannoni elena.zannoni@oracle.com
442 elf reader Elena Zannoni elena.zannoni@oracle.com
443 stabs reader Elena Zannoni elena.zannoni@oracle.com
444 readline/ Elena Zannoni elena.zannoni@oracle.com
445 NetBSD native & host Jason Thorpe thorpej@netbsd.org
446 Pascal support Pierre Muller muller@sourceware.org
447 avr Theodore A. Roth troth@openavr.org
448 Modula-2 support Gaius Mulley gaius@glam.ac.uk
449
450
451 Write After Approval
452 (alphabetic)
453
454 To get recommended for the Write After Approval list you need a valid
455 FSF assignment and have submitted one good patch.
456
457 Pedro Alves pedro_alves@portugalmail.pt
458 David Anderson davea@sgi.com
459 John David Anglin dave.anglin@nrc-cnrc.gc.ca
460 Shrinivas Atre shrinivasa@kpitcummins.com
461 Sterling Augustine saugustine@google.com
462 Scott Bambrough scottb@netwinder.org
463 Thiago Jung Bauermann bauerman@br.ibm.com
464 Jon Beniston jon@beniston.com
465 Gary Benson gbenson@redhat.com
466 Jan Beulich jbeulich@novell.com
467 Jim Blandy jimb@codesourcery.com
468 Philip Blundell philb@gnu.org
469 Eric Botcazou ebotcazou@libertysurf.fr
470 Per Bothner per@bothner.com
471 Joel Brobecker brobecker@adacore.com
472 Dave Brolley brolley@redhat.com
473 Paul Brook paul@codesourcery.com
474 Julian Brown julian@codesourcery.com
475 Kevin Buettner kevinb@redhat.com
476 Andrew Burgess aburgess@broadcom.com
477 Andrew Cagney cagney@gnu.org
478 David Carlton carlton@bactrian.org
479 Stephane Carrez Stephane.Carrez@gmail.com
480 Michael Chastain mec.gnu@mindspring.com
481 Renquan Cheng crq@gcc.gnu.org
482 Eric Christopher echristo@apple.com
483 Randolph Chung tausq@debian.org
484 Nick Clifton nickc@redhat.com
485 J.T. Conklin jtc@acorntoolworks.com
486 Brendan Conoboy blc@redhat.com
487 Ludovic Courtès ludo@gnu.org
488 Sanjoy Das sanjoy@playingwithpointers.com
489 Jean-Charles Delay delay@adacore.com
490 DJ Delorie dj@redhat.com
491 Chris Demetriou cgd@google.com
492 Philippe De Muyter phdm@macqel.be
493 Dhananjay Deshpande dhananjayd@kpitcummins.com
494 Markus Deuling deuling@de.ibm.com
495 Klee Dienes kdienes@apple.com
496 Gabriel Dos Reis gdr@integrable-solutions.net
497 Sergio Durigan Junior sergiodj@redhat.com
498 Michael Eager eager@eagercon.com
499 Richard Earnshaw rearnsha@arm.com
500 Steve Ellcey sje@cup.hp.com
501 Frank Ch. Eigler fche@redhat.com
502 Ben Elliston bje@gnu.org
503 Doug Evans dje@google.com
504 Adam Fedor fedor@gnu.org
505 Brian Ford ford@vss.fsi.com
506 Orjan Friberg orjanf@axis.com
507 Nathan Froyd froydnj@codesourcery.com
508 Gary Funck gary@intrepid.com
509 Paul Gilliam pgilliam@us.ibm.com
510 Tristan Gingold gingold@adacore.com
511 Anton Gorenkov xgsa@yandex.ru
512 Raoul Gough RaoulGough@yahoo.co.uk
513 Anthony Green green@redhat.com
514 Matthew Green mrg@eterna.com.au
515 Matthew Gretton-Dann matthew.gretton-dann@arm.com
516 Maxim Grigoriev maxim2405@gmail.com
517 Jerome Guitton guitton@act-europe.fr
518 Ben Harris bjh21@netbsd.org
519 Richard Henderson rth@redhat.com
520 Aldy Hernandez aldyh@redhat.com
521 Paul Hilfinger hilfinger@gnat.com
522 Matt Hiller hiller@redhat.com
523 Kazu Hirata kazu@cs.umass.edu
524 Jeff Holcomb jeffh@redhat.com
525 Don Howard dhoward@redhat.com
526 Nick Hudson nick.hudson@dsl.pipex.com
527 Martin Hunt hunt@redhat.com
528 Meador Inge meadori@codesourcery.com
529 Jim Ingham jingham@apple.com
530 Baurzhan Ismagulov ibr@radix50.net
531 Manoj Iyer manjo@austin.ibm.com
532 Daniel Jacobowitz drow@false.org
533 Andreas Jaeger aj@suse.de
534 Janis Johnson janisjo@codesourcery.com
535 Jeff Johnston jjohnstn@redhat.com
536 Geoff Keating geoffk@redhat.com
537 Mark Kettenis kettenis@gnu.org
538 Marc Khouzam marc.khouzam@ericsson.com
539 Jim Kingdon kingdon@panix.com
540 Paul Koning paul_koning@dell.com
541 Jan Kratochvil jan.kratochvil@redhat.com
542 Jonathan Larmour jifl@ecoscentric.com
543 Jeff Law law@redhat.com
544 Justin Lebar justin.lebar@gmail.com
545 David Lecomber david@streamline-computing.com
546 Don Lee don.lee@sunplusct.com
547 Robert Lipe rjl@sco.com
548 Sandra Loosemore sandra@codesourcery.com
549 H.J. Lu hjl.tools@gmail.com
550 Michal Ludvig mludvig@suse.cz
551 Edjunior B. Machado emachado@linux.vnet.ibm.com
552 Luis Machado lgustavo@codesourcery.com
553 Glen McCready gkm@redhat.com
554 Greg McGary greg@mcgary.org
555 Roland McGrath roland@redhat.com
556 Bryce McKinlay mckinlay@redhat.com
557 Jason Merrill jason@redhat.com
558 David S. Miller davem@redhat.com
559 Mark Mitchell mark@codesourcery.com
560 Marko Mlinar markom@opencores.org
561 Alan Modra amodra@gmail.com
562 Fawzi Mohamed fawzi.mohamed@nokia.com
563 Jason Molenda jmolenda@apple.com
564 Chris Moller cmoller@redhat.com
565 Phil Muldoon pmuldoon@redhat.com
566 Pierre Muller muller@sourceware.org
567 Gaius Mulley gaius@glam.ac.uk
568 Masaki Muranaka monaka@monami-software.com
569 Joseph Myers joseph@codesourcery.com
570 Fernando Nasser fnasser@redhat.com
571 Adam Nemet anemet@caviumnetworks.com
572 Nathanael Nerode neroden@gcc.gnu.org
573 Hans-Peter Nilsson hp@bitrange.com
574 David O'Brien obrien@freebsd.org
575 Alexandre Oliva aoliva@redhat.com
576 Karen Osmond karen.osmond@gmail.com
577 Pawandeep Oza oza.pawandeep@gmail.com
578 Denis Pilat denis.pilat@st.com
579 Andrew Pinski apinski@cavium.com
580 Kevin Pouget kevin.pouget@st.com
581 Paul Pluzhnikov ppluzhnikov@google.com
582 Marek Polacek mpolacek@redhat.com
583 Siddhesh Poyarekar siddhesh@redhat.com
584 Vladimir Prus vladimir@codesourcery.com
585 Yao Qi yao@codesourcery.com
586 Qinwei qinwei@sunnorth.com.cn
587 Siva Chandra Reddy sivachandra@google.com
588 Matt Rice ratmice@gmail.com
589 Frederic Riss frederic.riss@st.com
590 Aleksandar Ristovski aristovski@qnx.com
591 Tom Rix trix@redhat.com
592 Nick Roberts nickrob@snap.net.nz
593 Bob Rossi bob_rossi@cox.net
594 Theodore A. Roth troth@openavr.org
595 Ian Roxborough irox@redhat.com
596 Maciej W. Rozycki macro@linux-mips.org
597 Grace Sainsbury graces@redhat.com
598 Kei Sakamoto sakamoto.kei@renesas.com
599 Mark Salter msalter@redhat.com
600 Richard Sandiford richard@codesourcery.com
601 Iain Sandoe iain@codesourcery.com
602 Peter Schauer Peter.Schauer@mytum.de
603 Andreas Schwab schwab@linux-m68k.org
604 Thomas Schwinge tschwinge@gnu.org
605 Keith Seitz keiths@redhat.com
606 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
607 Ozkan Sezer sezeroz@gmail.com
608 Stan Shebs stan@codesourcery.com
609 Joel Sherrill joel.sherrill@oarcorp.com
610 Mark Shinwell shinwell@codesourcery.com
611 Craig Silverstein csilvers@google.com
612 Aidan Skinner aidan@velvet.net
613 Jiri Smid smid@suse.cz
614 Andrey Smirnov andrew.smirnov@gmail.com
615 David Smith dsmith@redhat.com
616 Stephen P. Smith ischis2@cox.net
617 Jackie Smith Cashion jsmith@redhat.com
618 Petr Sorfa petrs@caldera.com
619 Andrew Stubbs ams@codesourcery.com
620 Emi Suzuki emi-suzuki@tjsys.co.jp
621 Ian Lance Taylor ian@airs.com
622 Gary Thomas gthomas@redhat.com
623 Jason Thorpe thorpej@netbsd.org
624 Caroline Tice ctice@apple.com
625 Kai Tietz ktietz@redhat.com
626 Andreas Tobler andreast@fgznet.ch
627 Tom Tromey tromey@redhat.com
628 David Ung davidu@mips.com
629 D Venkatasubramanian dvenkat@noida.hcltech.com
630 Corinna Vinschen vinschen@redhat.com
631 Sami Wagiaalla swagiaal@redhat.com
632 Keith Walker keith.walker@arm.com
633 Kris Warkentin kewarken@qnx.com
634 Philippe Waroquiers philippe.waroquiers@skynet.be
635 Ulrich Weigand uweigand@de.ibm.com
636 Ken Werner ken.werner@de.ibm.com
637 Mark Wielaard mjw@redhat.com
638 Nathan Williams nathanw@wasabisystems.com
639 Bob Wilson bob.wilson@acm.org
640 Jim Wilson wilson@tuliptree.org
641 Mike Wrighton wrighton@codesourcery.com
642 Kwok Cheung Yeung kcy@codesourcery.com
643 Elena Zannoni elena.zannoni@oracle.com
644 Eli Zaretskii eliz@gnu.org
645 Jie Zhang jzhang918@gmail.com
646 Wu Zhou woodzltc@cn.ibm.com
647 Yoshinori Sato ysato@users.sourceforge.jp
648 Hui Zhu teawater@gmail.com
649 Khoo Yit Phang khooyp@cs.umd.edu
650
651 Past Maintainers
652
653 Whenever removing yourself, or someone else, from this file, consider
654 listing their areas of development here for posterity.
655
656 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
657 Jeff Law (hppa) law at cygnus dot com
658 Daniel Berlin (C++ support) dan at cgsoftware dot com
659 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
660 David Taylor (d10v, sparc, utils, defs,
661 expression evaluator, language support) taylor at candd dot org
662 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
663 Frank Ch. Eigler (sim) fche at redhat dot com
664 Per Bothner (Java) per at bothner dot com
665 Anthony Green (Java) green at redhat dot com
666 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
667 Mark Salter (testsuite/lib+config) msalter at redhat dot com
668 Jim Kingdon (web pages) kingdon at panix dot com
669 Jim Ingham (gdbtk, libgui) jingham at apple dot com
670 Mark Kettenis (hurd native) kettenis at gnu dot org
671 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
672 Robert Lipe (SCO/Unixware) rjl at sco dot com
673 Peter Schauer (global, AIX, xcoffsolib,
674 Solaris/x86) Peter.Schauer at mytum dot de
675 Scott Bambrough (ARM) scottb at netwinder dot org
676 Philippe De Muyter (coff) phdm at macqel dot be
677 Michael Chastain (testsuite) mec.gnu at mindspring dot com
678 Fred Fish (global)
679 Jim Blandy (global) jimb@red-bean.com
680 Michael Snyder (global)
681 Christopher Faylor (MS Windows, host & native)
682
683
684 Folks that have been caught up in a paper trail:
685
686 David Carlton carlton@bactrian.org
687 Ramana Radhakrishnan ramana.r@gmail.com
688
689 ;; Local Variables:
690 ;; coding: utf-8
691 ;; End: