projects / binutils-gdb.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
history | raw | HEAD
* jv-lang.c (jv_type_objfile_data_key, dynamics_objfile)
[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 Andrew Cagney (Red Hat)
119 Robert Dewar (AdaCore, NYU)
120 Klee Dienes (Apple)
121 Paul Hilfinger (UC Berkeley)
122 Dan Jacobowitz (Google)
123 Stan Shebs (CodeSourcery)
124 Richard Stallman (FSF)
125 Ian Lance Taylor (Google)
126 Todd Whitesel
127
128
129 Global Maintainers
130 ------------------
131
132 The global maintainers may review and commit any change to GDB, except in
133 areas with a Responsible Maintainer available. For major changes, or
134 changes to areas with other active developers, global maintainers are
135 strongly encouraged to post their own patches for feedback before
136 committing.
137
138 The global maintainers are responsible for reviewing patches to any area
139 for which no Responsible Maintainer is listed.
140
141 Global maintainers also have the authority to revert patches which should
142 not have been applied, e.g. patches which were not approved, controversial
143 patches committed under the Obvious Fix Rule, patches with important bugs
144 that can't be immediately fixed, or patches which go against an accepted and
145 documented roadmap for GDB development. Any global maintainer may request
146 the reversion of a patch. If no global maintainer, or responsible
147 maintainer in the affected areas, supports the patch (except for the
148 maintainer who originally committed it), then after 48 hours the maintainer
149 who called for the reversion may revert the patch.
150
151 No one may reapply a reverted patch without the agreement of the maintainer
152 who reverted it, or bringing the issue to the GDB Steering Committee for
153 discussion.
154
155 At the moment there are no documented roadmaps for GDB development; in the
156 future, if there are, a reference to the list will be included here.
157
158 The current global maintainers are (in alphabetical order):
159
160 Pedro Alves pedro@codesourcery.com
161 Joel Brobecker brobecker@adacore.com
162 Kevin Buettner kevinb@redhat.com
163 Andrew Cagney cagney@gnu.org
164 Doug Evans dje@google.com
165 Daniel Jacobowitz drow@false.org
166 Mark Kettenis kettenis@gnu.org
167 Jan Kratochvil jan.kratochvil@redhat.com
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
257 avr --target=avr ,-Werror
258 Tristan Gingold gingold@adacore.com
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 Jan Kratochvil jan.kratochvil@redhat.com
273
274 lm32 --target=lm32-elf ,-Werror
275
276 m32c --target=m32c-elf ,-Werror
277
278 m32r --target=m32r-elf ,-Werror
279
280 m68hc11 --target=m68hc11-elf ,-Werror ,
281 Stephane Carrez stcarrez@nerim.fr
282
283 m68k --target=m68k-elf ,-Werror
284
285 m88k --target=m88k-openbsd ,-Werror
286 Mark Kettenis kettenis@gnu.org
287
288 mcore Deleted
289
290 mep --target=mep-elf ,-Werror
291 Kevin Buettner kevinb@redhat.com
292
293 microblaze --target=microblaze-xilinx-elf ,-Werror
294 --target=microblaze-linux-gnu ,-Werror
295 Michael Eager eager@eagercon.com
296
297 mips --target=mips-elf ,-Werror
298
299 mn10300 --target=mn10300-elf broken
300 (sim/ dies with make -j)
301 Michael Snyder msnyder@vmware.com
302
303 moxie --target=moxie-elf ,-Werror
304 Anthony Green green@moxielogic.com
305
306 ms1 --target=ms1-elf ,-Werror
307 Kevin Buettner kevinb@redhat.com
308
309 ns32k Deleted
310
311 pa --target=hppa-elf ,-Werror
312
313 powerpc --target=powerpc-eabi ,-Werror
314
315 s390 --target=s390-linux-gnu ,-Werror
316
317 score --target=score-elf
318 Qinwei qinwei@sunnorth.com.cn
319
320 sh --target=sh-elf ,-Werror
321 --target=sh64-elf ,-Werror
322
323 sparc --target=sparc64-solaris2.10 ,-Werror
324 (--target=sparc-elf broken)
325
326 spu --target=spu-elf ,-Werror
327 Ulrich Weigand uweigand@de.ibm.com
328
329 v850 --target=v850-elf ,-Werror
330
331 vax --target=vax-netbsd ,-Werror
332
333 x86-64 --target=x86_64-linux-gnu ,-Werror
334
335 xstormy16 --target=xstormy16-elf
336 Corinna Vinschen vinschen@redhat.com
337
338 xtensa --target=xtensa-elf
339 Maxim Grigoriev maxim2405@gmail.com
340
341 All developers recognized by this file can make arbitrary changes to
342 OBSOLETE targets.
343
344 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
345 above targets.
346
347
348 Host/Native:
349
350 The Native maintainer is responsible for target specific native
351 support - typically shared libraries and quirks to procfs/ptrace/...
352 The Native maintainer works with the Arch and Core maintainers when
353 resolving more generic problems.
354
355 The host maintainer ensures that gdb can be built as a cross debugger on
356 their platform.
357
358 AIX Joel Brobecker brobecker@adacore.com
359 Darwin Tristan Gingold gingold@adacore.com
360 djgpp native Eli Zaretskii eliz@gnu.org
361 GNU Hurd Alfred M. Szmidt ams@gnu.org
362 MS Windows (NT, '00, 9x, Me, XP) host & native
363 Chris Faylor cgf@alum.bu.edu
364 GNU/Linux/x86 native & host
365 Mark Kettenis kettenis@gnu.org
366 GNU/Linux MIPS native & host
367 Daniel Jacobowitz drow@false.org
368 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
369 FreeBSD native & host Mark Kettenis kettenis@gnu.org
370
371
372
373 Core: Generic components used by all of GDB
374
375 tracing Michael Snyder msnyder@vmware.com
376 threads Michael Snyder msnyder@vmware.com
377 Mark Kettenis kettenis@gnu.org
378 language support
379 Ada Joel Brobecker brobecker@adacore.com
380 Paul Hilfinger hilfinger@gnat.com
381 C++ Daniel Jacobowitz drow@false.org
382 Objective C support Adam Fedor fedor@gnu.org
383 shared libs Kevin Buettner kevinb@redhat.com
384 MI interface Vladimir Prus vladimir@codesourcery.com
385
386 documentation Eli Zaretskii eliz@gnu.org
387 (including NEWS)
388 testsuite
389 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
390 threads (gdb.threads) Michael Snyder msnyder@vmware.com
391 trace (gdb.trace) Michael Snyder msnyder@vmware.com
392
393
394 UI: External (user) interfaces.
395
396 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
397 Keith Seitz keiths@redhat.com
398 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
399
400
401 Misc:
402
403 gdb/gdbserver Daniel Jacobowitz drow@false.org
404
405 Makefile.in, configure* ALL
406
407 mmalloc/ ALL Host maintainers
408
409 sim/ See sim/MAINTAINERS
410
411 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
412 ALL
413 Host maintainers (host dependant parts)
414 (but get your changes into the master version)
415
416 tcl/ tk/ itcl/ ALL
417
418
419 Authorized Committers
420 ---------------------
421
422 These are developers working on particular areas of GDB, who are trusted to
423 commit their own (or other developers') patches in those areas without
424 further review from a Global Maintainer or Responsible Maintainer. They are
425 under no obligation to review posted patches - but, of course, are invited
426 to do so!
427
428 PowerPC Andrew Cagney cagney@gnu.org
429 ARM Richard Earnshaw rearnsha@arm.com
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 Gary Benson gbenson@redhat.com
472 Jan Beulich jbeulich@novell.com
473 Jim Blandy jimb@codesourcery.com
474 Philip Blundell philb@gnu.org
475 Per Bothner per@bothner.com
476 Joel Brobecker brobecker@adacore.com
477 Dave Brolley brolley@redhat.com
478 Paul Brook paul@codesourcery.com
479 Julian Brown julian@codesourcery.com
480 Kevin Buettner kevinb@redhat.com
481 Andrew Cagney cagney@gnu.org
482 David Carlton carlton@bactrian.org
483 Stephane Carrez stcarrez@nerim.fr
484 Michael Chastain mec.gnu@mindspring.com
485 Renquan Cheng crq@gcc.gnu.org
486 Eric Christopher echristo@apple.com
487 Randolph Chung tausq@debian.org
488 Nick Clifton nickc@redhat.com
489 J.T. Conklin jtc@acorntoolworks.com
490 Brendan Conoboy blc@redhat.com
491 Ludovic Courtès ludo@gnu.org
492 DJ Delorie dj@redhat.com
493 Chris Demetriou cgd@google.com
494 Philippe De Muyter phdm@macqel.be
495 Dhananjay Deshpande dhananjayd@kpitcummins.com
496 Markus Deuling deuling@de.ibm.com
497 Klee Dienes kdienes@apple.com
498 Gabriel Dos Reis gdr@integrable-solutions.net
499 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
500 Michael Eager eager@eagercon.com
501 Richard Earnshaw rearnsha@arm.com
502 Steve Ellcey sje@cup.hp.com
503 Frank Ch. Eigler fche@redhat.com
504 Ben Elliston bje@gnu.org
505 Doug Evans dje@google.com
506 Adam Fedor fedor@gnu.org
507 Brian Ford ford@vss.fsi.com
508 Orjan Friberg orjanf@axis.com
509 Nathan Froyd froydnj@codesourcery.com
510 Gary Funck gary@intrepid.com
511 Paul Gilliam pgilliam@us.ibm.com
512 Tristan Gingold gingold@adacore.com
513 Raoul Gough RaoulGough@yahoo.co.uk
514 Anthony Green green@redhat.com
515 Matthew Green mrg@eterna.com.au
516 Matthew Gretton-Dann matthew.gretton-dann@arm.com
517 Maxim Grigoriev maxim2405@gmail.com
518 Jerome Guitton guitton@act-europe.fr
519 Ben Harris bjh21@netbsd.org
520 Richard Henderson rth@redhat.com
521 Aldy Hernandez aldyh@redhat.com
522 Paul Hilfinger hilfinger@gnat.com
523 Matt Hiller hiller@redhat.com
524 Kazu Hirata kazu@cs.umass.edu
525 Jeff Holcomb jeffh@redhat.com
526 Don Howard dhoward@redhat.com
527 Nick Hudson nick.hudson@dsl.pipex.com
528 Martin Hunt hunt@redhat.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 Jan Kratochvil jan.kratochvil@redhat.com
541 Jonathan Larmour jifl@ecoscentric.com
542 Jeff Law law@redhat.com
543 David Lecomber david@streamline-computing.com
544 Don Lee don.lee@sunplusct.com
545 Robert Lipe rjl@sco.com
546 Sandra Loosemore sandra@codesourcery.com
547 H.J. Lu hjl.tools@gmail.com
548 Michal Ludvig mludvig@suse.cz
549 Edjunior B. Machado emachado@linux.vnet.ibm.com
550 Luis Machado lgustavo@codesourcery.com
551 Glen McCready gkm@redhat.com
552 Greg McGary greg@mcgary.org
553 Roland McGrath roland@redhat.com
554 Bryce McKinlay mckinlay@redhat.com
555 Jason Merrill jason@redhat.com
556 David S. Miller davem@redhat.com
557 Mark Mitchell mark@codesourcery.com
558 Marko Mlinar markom@opencores.org
559 Alan Modra amodra@gmail.com
560 Jason Molenda jmolenda@apple.com
561 Chris Moller cmoller@redhat.com
562 Phil Muldoon pmuldoon@redhat.com
563 Pierre Muller muller@sourceware.org
564 Gaius Mulley gaius@glam.ac.uk
565 Masaki Muranaka monaka@monami-software.com
566 Joseph Myers joseph@codesourcery.com
567 Fernando Nasser fnasser@redhat.com
568 Adam Nemet anemet@caviumnetworks.com
569 Nathanael Nerode neroden@gcc.gnu.org
570 Hans-Peter Nilsson hp@bitrange.com
571 David O'Brien obrien@freebsd.org
572 Alexandre Oliva aoliva@redhat.com
573 Karen Osmond karen.osmond@gmail.com
574 Denis Pilat denis.pilat@st.com
575 Paul Pluzhnikov ppluzhnikov@google.com
576 Marek Polacek mpolacek@redhat.com
577 Vladimir Prus vladimir@codesourcery.com
578 Yao Qi yao@codesourcery.com
579 Qinwei qinwei@sunnorth.com.cn
580 Frederic Riss frederic.riss@st.com
581 Aleksandar Ristovski aristovski@qnx.com
582 Tom Rix trix@redhat.com
583 Nick Roberts nickrob@snap.net.nz
584 Bob Rossi bob_rossi@cox.net
585 Theodore A. Roth troth@openavr.org
586 Ian Roxborough irox@redhat.com
587 Maciej W. Rozycki macro@linux-mips.org
588 Grace Sainsbury graces@redhat.com
589 Kei Sakamoto sakamoto.kei@renesas.com
590 Mark Salter msalter@redhat.com
591 Richard Sandiford richard@codesourcery.com
592 Peter Schauer Peter.Schauer@mytum.de
593 Andreas Schwab schwab@linux-m68k.org
594 Thomas Schwinge tschwinge@gnu.org
595 Keith Seitz keiths@redhat.com
596 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
597 Ozkan Sezer sezeroz@gmail.com
598 Stan Shebs stan@codesourcery.com
599 Joel Sherrill joel.sherrill@oarcorp.com
600 Mark Shinwell shinwell@codesourcery.com
601 Craig Silverstein csilvers@google.com
602 Aidan Skinner aidan@velvet.net
603 Jiri Smid smid@suse.cz
604 David Smith dsmith@redhat.com
605 Stephen P. Smith ischis2@cox.net
606 Jackie Smith Cashion jsmith@redhat.com
607 Michael Snyder msnyder@vmware.com
608 Petr Sorfa petrs@caldera.com
609 Andrew Stubbs ams@codesourcery.com
610 Emi Suzuki emi-suzuki@tjsys.co.jp
611 Ian Lance Taylor ian@airs.com
612 Gary Thomas gthomas@redhat.com
613 Jason Thorpe thorpej@netbsd.org
614 Caroline Tice ctice@apple.com
615 Kai Tietz ktietz@redhat.com
616 Andreas Tobler andreast@fgznet.ch
617 Tom Tromey tromey@redhat.com
618 David Ung davidu@mips.com
619 D Venkatasubramanian dvenkat@noida.hcltech.com
620 Corinna Vinschen vinschen@redhat.com
621 Sami Wagiaalla swagiaal@redhat.com
622 Keith Walker keith.walker@arm.com
623 Kris Warkentin kewarken@qnx.com
624 Ulrich Weigand uweigand@de.ibm.com
625 Ken Werner ken.werner@de.ibm.com
626 Nathan Williams nathanw@wasabisystems.com
627 Bob Wilson bob.wilson@acm.org
628 Jim Wilson wilson@tuliptree.org
629 Kwok Cheung Yeung kcy@codesourcery.com
630 Elena Zannoni elena.zannoni@oracle.com
631 Eli Zaretskii eliz@gnu.org
632 Jie Zhang jzhang918@gmail.com
633 Wu Zhou woodzltc@cn.ibm.com
634 Yoshinori Sato ysato@users.sourceforge.jp
635 Hui Zhu teawater@gmail.com
636
637
638 Past Maintainers
639
640 Whenever removing yourself, or someone else, from this file, consider
641 listing their areas of development here for posterity.
642
643 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
644 Jeff Law (hppa) law at cygnus dot com
645 Daniel Berlin (C++ support) dan at cgsoftware dot com
646 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
647 David Taylor (d10v, sparc, utils, defs,
648 expression evaluator, language support) taylor at candd dot org
649 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
650 Frank Ch. Eigler (sim) fche at redhat dot com
651 Per Bothner (Java) per at bothner dot com
652 Anthony Green (Java) green at redhat dot com
653 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
654 Mark Salter (testsuite/lib+config) msalter at redhat dot com
655 Jim Kingdon (web pages) kingdon at panix dot com
656 Jim Ingham (gdbtk, libgui) jingham at apple dot com
657 Mark Kettenis (hurd native) kettenis at gnu dot org
658 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
659 Robert Lipe (SCO/Unixware) rjl at sco dot com
660 Peter Schauer (global, AIX, xcoffsolib,
661 Solaris/x86) Peter.Schauer at mytum dot de
662 Scott Bambrough (ARM) scottb at netwinder dot org
663 Philippe De Muyter (coff) phdm at macqel dot be
664 Michael Chastain (testsuite) mec.gnu at mindspring dot com
665 Fred Fish (global)
666 Jim Blandy (global) jimb@red-bean.com
667
668
669
670 Folks that have been caught up in a paper trail:
671
672 David Carlton carlton@bactrian.org
673 Ramana Radhakrishnan ramana.r@gmail.com
674
675 ;; Local Variables:
676 ;; coding: utf-8
677 ;; End: