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