../commit.txt~
[deliverable/binutils-gdb.git] / gdb / MAINTAINERS
1 GDB Maintainers
2 ===============
3
4
5 Overview
6 --------
7
8 This file describes different groups of people who are, together, the
9 maintainers and developers of the GDB project. Don't worry - it sounds
10 more complicated than it really is.
11
12 There are four groups of GDB developers, covering the patch development and
13 review process:
14
15 - The Global Maintainers.
16
17 These are the developers in charge of most daily development. They
18 have wide authority to apply and reject patches, but defer to the
19 Responsible Maintainers (see below) within their spheres of
20 responsibility.
21
22 - The Responsible Maintainers.
23
24 These are developers who have expertise and interest in a particular
25 area of GDB, who are generally available to review patches, and who
26 prefer to enforce a single vision within their areas.
27
28 - The Authorized Committers.
29
30 These are developers who are trusted to make changes within a specific
31 area of GDB without additional oversight.
32
33 - The Write After Approval Maintainers.
34
35 These are developers who have write access to the GDB source tree. They
36 can check in their own changes once a developer with the appropriate
37 authority has approved the changes; they can also apply the Obvious
38 Fix Rule (below).
39
40 All maintainers are encouraged to post major patches to the gdb-patches
41 mailing list for comments, even if they have the authority to commit the
42 patch without review from another maintainer. This especially includes
43 patches which change internal interfaces (e.g. global functions, data
44 structures) or external interfaces (e.g. user, remote, MI, et cetera).
45
46 The term "review" is used in this file to describe several kinds of feedback
47 from a maintainer: approval, rejection, and requests for changes or
48 clarification with the intention of approving a revised version. Review is
49 a privilege and/or responsibility of various positions among the GDB
50 Maintainers. Of course, anyone - whether they hold a position but not the
51 relevant one for a particular patch, or are just following along on the
52 mailing lists for fun, or anything in between - may suggest changes or
53 ask questions about a patch!
54
55 There's also a couple of other people who play special roles in the GDB
56 community, separately from the patch process:
57
58 - The GDB Steering Committee.
59
60 These are the official (FSF-appointed) maintainers of GDB. They have
61 final and overriding authority for all GDB-related decisions, including
62 anything described in this file. The committee is not generally
63 involved in day-to-day development (although its members may be, as
64 individuals).
65
66 - The Release Manager.
67
68 This developer is in charge of making new releases of GDB.
69
70 - The Patch Champions.
71
72 These volunteers make sure that no contribution is overlooked or
73 forgotten.
74
75 Most changes to the list of maintainers in this file are handled by
76 consensus among the global maintainers and any other involved parties.
77 In cases where consensus can not be reached, the global maintainers may
78 ask the Steering Committee for a final decision.
79
80
81 The Obvious Fix Rule
82 --------------------
83
84 All maintainers listed in this file, including the Write After Approval
85 developers, are allowed to check in obvious fixes.
86
87 An "obvious fix" means that there is no possibility that anyone will
88 disagree with the change.
89
90 A good mental test is "will the person who hates my work the most be
91 able to find fault with the change" - if so, then it's not obvious and
92 needs to be posted first. :-)
93
94 Something like changing or bypassing an interface is _not_ an obvious
95 fix, since such a change without discussion will result in
96 instantaneous and loud complaints.
97
98 For documentation changes, about the only kind of fix that is obvious
99 is correction of a typo or bad English usage.
100
101
102 GDB Steering Committee
103 ----------------------
104
105 The members of the GDB Steering Committee are the FSF-appointed
106 maintainers of the GDB project.
107
108 The Steering Committee has final authority for all GDB-related topics;
109 they may make whatever changes that they deem necessary, or that the FSF
110 requests. However, they are generally not involved in day-to-day
111 development.
112
113 The current members of the steering committee are listed below, in
114 alphabetical order. Their affiliations are provided for reference only -
115 their membership on the Steering Committee is individual and not through
116 their affiliation, and they act on behalf of the GNU project.
117
118 Jim Blandy (Mozilla)
119 Andrew Cagney (Red Hat)
120 Robert Dewar (AdaCore, NYU)
121 Klee Dienes (Apple)
122 Paul Hilfinger (UC Berkeley)
123 Dan Jacobowitz (CodeSourcery)
124 Stan Shebs (CodeSourcery)
125 Richard Stallman (FSF)
126 Ian Lance Taylor (C2)
127 Todd Whitesel
128
129
130 Global Maintainers
131 ------------------
132
133 The global maintainers may review and commit any change to GDB, except in
134 areas with a Responsible Maintainer available. For major changes, or
135 changes to areas with other active developers, global maintainers are
136 strongly encouraged to post their own patches for feedback before
137 committing.
138
139 The global maintainers are responsible for reviewing patches to any area
140 for which no Responsible Maintainer is listed.
141
142 Global maintainers also have the authority to revert patches which should
143 not have been applied, e.g. patches which were not approved, controversial
144 patches committed under the Obvious Fix Rule, patches with important bugs
145 that can't be immediately fixed, or patches which go against an accepted and
146 documented roadmap for GDB development. Any global maintainer may request
147 the reversion of a patch. If no global maintainer, or responsible
148 maintainer in the affected areas, supports the patch (except for the
149 maintainer who originally committed it), then after 48 hours the maintainer
150 who called for the reversion may revert the patch.
151
152 No one may reapply a reverted patch without the agreement of the maintainer
153 who reverted it, or bringing the issue to the GDB Steering Committee for
154 discussion.
155
156 At the moment there are no documented roadmaps for GDB development; in the
157 future, if there are, a reference to the list will be included here.
158
159 The current global maintainers are (in alphabetical order):
160
161 Pedro Alves pedro@codesourcery.com
162 Jim Blandy jimb@red-bean.com
163 Joel Brobecker brobecker@adacore.com
164 Kevin Buettner kevinb@redhat.com
165 Andrew Cagney cagney@gnu.org
166 Doug Evans dje@google.com
167 Daniel Jacobowitz dan@codesourcery.com
168 Mark Kettenis kettenis@gnu.org
169 Jan Kratochvil jan.kratochvil@redhat.com
170 Stan Shebs stan@codesourcery.com
171 Michael Snyder msnyder@vmware.com
172 Tom Tromey tromey@redhat.com
173 Ulrich Weigand Ulrich.Weigand@de.ibm.com
174 Elena Zannoni elena.zannoni@oracle.com
175 Eli Zaretskii eliz@gnu.org
176
177
178 Release Manager
179 ---------------
180
181 The current release manager is: Joel Brobecker <brobecker@adacore.com>
182
183 His responsibilities are:
184
185 * organizing, scheduling, and managing releases of GDB.
186
187 * deciding the approval and commit policies for release branches,
188 and can change them as needed.
189
190
191
192 Patch Champions
193 ---------------
194
195 These volunteers track all patches submitted to the gdb-patches list. They
196 endeavor to prevent any posted patch from being overlooked; work with
197 contributors to meet GDB's coding style and general requirements, along with
198 FSF copyright assignments; remind (ping) responsible maintainers to review
199 patches; and ensure that contributors are given credit.
200
201 Current patch champions (in alphabetical order):
202
203 Randolph Chung <tausq@debian.org>
204
205
206
207 Responsible Maintainers
208 -----------------------
209
210 These developers have agreed to review patches in specific areas of GDB, in
211 which they have knowledge and experience. These areas are generally broad;
212 the role of a responsible maintainer is to provide coherent and cohesive
213 structure within their area of GDB, to assure that patches from many
214 different contributors all work together for the best results.
215
216 Global maintainers will defer to responsible maintainers within their areas,
217 as long as the responsible maintainer is active. Active means that
218 responsible maintainers agree to review submitted patches in their area
219 promptly; patches and followups should generally be answered within a week.
220 If a responsible maintainer is interested in reviewing a patch but will not
221 have time within a week of posting, the maintainer should send an
222 acknowledgement of the patch to the gdb-patches mailing list, and
223 plan to follow up with a review within a month. These deadlines are for
224 initial responses to a patch - if the maintainer has suggestions
225 or questions, it may take an extended discussion before the patch
226 is ready to commit. There are no written requirements for discussion,
227 but maintainers are asked to be responsive.
228
229 If a responsible maintainer misses these deadlines occasionally (e.g.
230 vacation or unexpected workload), it's not a disaster - any global
231 maintainer may step in to review the patch. But sometimes life intervenes
232 more permanently, and a maintainer may no longer have time for these duties.
233 When this happens, he or she should step down (either into the Authorized
234 Committers section if still interested in the area, or simply removed from
235 the list of Responsible Maintainers if not).
236
237 If a responsible maintainer is unresponsive for an extended period of time
238 without stepping down, please contact the Global Maintainers; they will try
239 to contact the maintainer directly and fix the problem - potentially by
240 removing that maintainer from their listed position.
241
242 If there are several maintainers for a given domain then any one of them
243 may review a submitted patch.
244
245 Target Instruction Set Architectures:
246
247 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
248 (Operating System / Application Binary Interface) issues including CPU
249 variants.
250
251 The Target/Architecture maintainer works with the host maintainer when
252 resolving build issues. The Target/Architecture maintainer works with
253 the native maintainer when resolving ABI issues.
254
255 alpha --target=alpha-elf ,-Werror
256
257 arm --target=arm-elf ,-Werror
258
259 avr --target=avr ,-Werror
260 Tristan Gingold gingold@adacore.com
261
262 cris --target=cris-elf ,-Werror ,
263 (sim does not build with -Werror)
264
265 frv --target=frv-elf ,-Werror
266
267 h8300 --target=h8300-elf ,-Werror
268
269 i386 --target=i386-elf ,-Werror
270 Mark Kettenis kettenis@gnu.org
271
272 ia64 --target=ia64-linux-gnu ,-Werror
273 (--target=ia64-elf broken)
274 Jan Kratochvil jan.kratochvil@redhat.com
275
276 lm32 --target=lm32-elf ,-Werror
277
278 m32c --target=m32c-elf ,-Werror
279
280 m32r --target=m32r-elf ,-Werror
281
282 m68hc11 --target=m68hc11-elf ,-Werror ,
283 Stephane Carrez stcarrez@nerim.fr
284
285 m68k --target=m68k-elf ,-Werror
286
287 m88k --target=m88k-openbsd ,-Werror
288 Mark Kettenis kettenis@gnu.org
289
290 mcore Deleted
291
292 mep --target=mep-elf ,-Werror
293 Kevin Buettner kevinb@redhat.com
294
295 microblaze --target=microblaze-xilinx-elf ,-Werror
296 --target=microblaze-linux-gnu ,-Werror
297 Michael Eager eager@eagercon.com
298
299 mips --target=mips-elf ,-Werror
300
301 mn10300 --target=mn10300-elf broken
302 (sim/ dies with make -j)
303 Michael Snyder msnyder@vmware.com
304
305 moxie --target=moxie-elf ,-Werror
306 Anthony Green green@moxielogic.com
307
308 ms1 --target=ms1-elf ,-Werror
309 Kevin Buettner kevinb@redhat.com
310
311 ns32k Deleted
312
313 pa --target=hppa-elf ,-Werror
314
315 powerpc --target=powerpc-eabi ,-Werror
316
317 s390 --target=s390-linux-gnu ,-Werror
318
319 score --target=score-elf
320 Qinwei qinwei@sunnorth.com.cn
321
322 sh --target=sh-elf ,-Werror
323 --target=sh64-elf ,-Werror
324
325 sparc --target=sparc64-solaris2.10 ,-Werror
326 (--target=sparc-elf broken)
327
328 spu --target=spu-elf ,-Werror
329 Ulrich Weigand uweigand@de.ibm.com
330
331 v850 --target=v850-elf ,-Werror
332
333 vax --target=vax-netbsd ,-Werror
334
335 x86-64 --target=x86_64-linux-gnu ,-Werror
336
337 xstormy16 --target=xstormy16-elf
338 Corinna Vinschen vinschen@redhat.com
339
340 xtensa --target=xtensa-elf
341 Maxim Grigoriev maxim2405@gmail.com
342
343 All developers recognized by this file can make arbitrary changes to
344 OBSOLETE targets.
345
346 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
347 above targets.
348
349
350 Host/Native:
351
352 The Native maintainer is responsible for target specific native
353 support - typically shared libraries and quirks to procfs/ptrace/...
354 The Native maintainer works with the Arch and Core maintainers when
355 resolving more generic problems.
356
357 The host maintainer ensures that gdb can be built as a cross debugger on
358 their platform.
359
360 AIX Joel Brobecker brobecker@adacore.com
361 Darwin Tristan Gingold gingold@adacore.com
362 djgpp native Eli Zaretskii eliz@gnu.org
363 GNU Hurd Alfred M. Szmidt ams@gnu.org
364 MS Windows (NT, '00, 9x, Me, XP) host & native
365 Chris Faylor cgf@alum.bu.edu
366 GNU/Linux/x86 native & host
367 Mark Kettenis kettenis@gnu.org
368 GNU/Linux MIPS native & host
369 Daniel Jacobowitz dan@codesourcery.com
370 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
371 FreeBSD native & host Mark Kettenis kettenis@gnu.org
372
373
374
375 Core: Generic components used by all of GDB
376
377 tracing Michael Snyder msnyder@vmware.com
378 threads Michael Snyder msnyder@vmware.com
379 Mark Kettenis kettenis@gnu.org
380 language support
381 Ada Joel Brobecker brobecker@adacore.com
382 Paul Hilfinger hilfinger@gnat.com
383 C++ Daniel Jacobowitz dan@codesourcery.com
384 Objective C support Adam Fedor fedor@gnu.org
385 shared libs Kevin Buettner kevinb@redhat.com
386 MI interface Vladimir Prus vladimir@codesourcery.com
387
388 documentation Eli Zaretskii eliz@gnu.org
389 (including NEWS)
390 testsuite
391 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
392 threads (gdb.threads) Michael Snyder msnyder@vmware.com
393 trace (gdb.trace) Michael Snyder msnyder@vmware.com
394
395
396 UI: External (user) interfaces.
397
398 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
399 Keith Seitz keiths@redhat.com
400 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
401
402
403 Misc:
404
405 gdb/gdbserver Daniel Jacobowitz dan@codesourcery.com
406
407 Makefile.in, configure* ALL
408
409 mmalloc/ ALL Host maintainers
410
411 sim/ See sim/MAINTAINERS
412
413 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
414 ALL
415 Host maintainers (host dependant parts)
416 (but get your changes into the master version)
417
418 tcl/ tk/ itcl/ ALL
419
420
421 Authorized Committers
422 ---------------------
423
424 These are developers working on particular areas of GDB, who are trusted to
425 commit their own (or other developers') patches in those areas without
426 further review from a Global Maintainer or Responsible Maintainer. They are
427 under no obligation to review posted patches - but, of course, are invited
428 to do so!
429
430 PowerPC Andrew Cagney cagney@gnu.org
431 ARM Richard Earnshaw rearnsha@arm.com
432 CRIS Hans-Peter Nilsson hp@axis.com
433 IA64 Jeff Johnston jjohnstn@redhat.com
434 MIPS Joel Brobecker brobecker@adacore.com
435 m32r Kei Sakamoto sakamoto.kei@renesas.com
436 PowerPC Kevin Buettner kevinb@redhat.com
437 CRIS Orjan Friberg orjanf@axis.com
438 HPPA Randolph Chung tausq@debian.org
439 S390 Ulrich Weigand uweigand@de.ibm.com
440 djgpp DJ Delorie dj@delorie.com
441 [Please use this address to contact DJ about DJGPP]
442 tui Stephane Carrez stcarrez@nerim.fr
443 ia64 Kevin Buettner kevinb@redhat.com
444 AIX Kevin Buettner kevinb@redhat.com
445 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
446 gdb.java tests Anthony Green green@redhat.com
447 FreeBSD native & host David O'Brien obrien@freebsd.org
448 event loop Elena Zannoni elena.zannoni@oracle.com
449 generic symtabs Elena Zannoni elena.zannoni@oracle.com
450 dwarf readers Elena Zannoni elena.zannoni@oracle.com
451 elf reader Elena Zannoni elena.zannoni@oracle.com
452 stabs reader Elena Zannoni elena.zannoni@oracle.com
453 readline/ Elena Zannoni elena.zannoni@oracle.com
454 NetBSD native & host Jason Thorpe thorpej@netbsd.org
455 Pascal support Pierre Muller muller@sourceware.org
456 avr Theodore A. Roth troth@openavr.org
457 Modula-2 support Gaius Mulley gaius@glam.ac.uk
458
459
460 Write After Approval
461 (alphabetic)
462
463 To get recommended for the Write After Approval list you need a valid
464 FSF assignment and have submitted one good patch.
465
466 Pedro Alves pedro_alves@portugalmail.pt
467 David Anderson davea@sgi.com
468 John David Anglin dave.anglin@nrc-cnrc.gc.ca
469 Shrinivas Atre shrinivasa@kpitcummins.com
470 Scott Bambrough scottb@netwinder.org
471 Thiago Jung Bauermann bauerman@br.ibm.com
472 Jon Beniston jon@beniston.com
473 Gary Benson gbenson@redhat.com
474 Jan Beulich jbeulich@novell.com
475 Jim Blandy jimb@codesourcery.com
476 Philip Blundell philb@gnu.org
477 Per Bothner per@bothner.com
478 Joel Brobecker brobecker@adacore.com
479 Dave Brolley brolley@redhat.com
480 Paul Brook paul@codesourcery.com
481 Julian Brown julian@codesourcery.com
482 Kevin Buettner kevinb@redhat.com
483 Andrew Cagney cagney@gnu.org
484 David Carlton carlton@bactrian.org
485 Stephane Carrez stcarrez@nerim.fr
486 Michael Chastain mec.gnu@mindspring.com
487 Renquan Cheng crq@gcc.gnu.org
488 Eric Christopher echristo@apple.com
489 Randolph Chung tausq@debian.org
490 Nick Clifton nickc@redhat.com
491 J.T. Conklin jtc@acorntoolworks.com
492 Brendan Conoboy blc@redhat.com
493 Ludovic Courtès ludo@gnu.org
494 DJ Delorie dj@redhat.com
495 Chris Demetriou cgd@google.com
496 Philippe De Muyter phdm@macqel.be
497 Dhananjay Deshpande dhananjayd@kpitcummins.com
498 Markus Deuling deuling@de.ibm.com
499 Klee Dienes kdienes@apple.com
500 Gabriel Dos Reis gdr@integrable-solutions.net
501 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
502 Michael Eager eager@eagercon.com
503 Richard Earnshaw rearnsha@arm.com
504 Steve Ellcey sje@cup.hp.com
505 Frank Ch. Eigler fche@redhat.com
506 Ben Elliston bje@gnu.org
507 Doug Evans dje@google.com
508 Adam Fedor fedor@gnu.org
509 Brian Ford ford@vss.fsi.com
510 Orjan Friberg orjanf@axis.com
511 Nathan Froyd froydnj@codesourcery.com
512 Gary Funck gary@intrepid.com
513 Paul Gilliam pgilliam@us.ibm.com
514 Tristan Gingold gingold@adacore.com
515 Raoul Gough RaoulGough@yahoo.co.uk
516 Anthony Green green@redhat.com
517 Matthew Green mrg@eterna.com.au
518 Matthew Gretton-Dann matthew.gretton-dann@arm.com
519 Maxim Grigoriev maxim2405@gmail.com
520 Jerome Guitton guitton@act-europe.fr
521 Ben Harris bjh21@netbsd.org
522 Richard Henderson rth@redhat.com
523 Aldy Hernandez aldyh@redhat.com
524 Paul Hilfinger hilfinger@gnat.com
525 Matt Hiller hiller@redhat.com
526 Kazu Hirata kazu@cs.umass.edu
527 Jeff Holcomb jeffh@redhat.com
528 Don Howard dhoward@redhat.com
529 Nick Hudson nick.hudson@dsl.pipex.com
530 Martin Hunt hunt@redhat.com
531 Jim Ingham jingham@apple.com
532 Baurzhan Ismagulov ibr@radix50.net
533 Manoj Iyer manjo@austin.ibm.com
534 Daniel Jacobowitz dan@codesourcery.com
535 Andreas Jaeger aj@suse.de
536 Janis Johnson janisjo@codesourcery.com
537 Jeff Johnston jjohnstn@redhat.com
538 Geoff Keating geoffk@redhat.com
539 Mark Kettenis kettenis@gnu.org
540 Marc Khouzam marc.khouzam@ericsson.com
541 Jim Kingdon kingdon@panix.com
542 Jan Kratochvil jan.kratochvil@redhat.com
543 Jonathan Larmour jifl@ecoscentric.com
544 Jeff Law law@redhat.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 Jason Molenda jmolenda@apple.com
563 Chris Moller cmoller@redhat.com
564 Phil Muldoon pmuldoon@redhat.com
565 Pierre Muller muller@sourceware.org
566 Gaius Mulley gaius@glam.ac.uk
567 Masaki Muranaka monaka@monami-software.com
568 Joseph Myers joseph@codesourcery.com
569 Fernando Nasser fnasser@redhat.com
570 Adam Nemet anemet@caviumnetworks.com
571 Nathanael Nerode neroden@gcc.gnu.org
572 Hans-Peter Nilsson hp@bitrange.com
573 David O'Brien obrien@freebsd.org
574 Alexandre Oliva aoliva@redhat.com
575 Karen Osmond karen.osmond@gmail.com
576 Denis Pilat denis.pilat@st.com
577 Paul Pluzhnikov ppluzhnikov@google.com
578 Marek Polacek mpolacek@redhat.com
579 Vladimir Prus vladimir@codesourcery.com
580 Yao Qi yao@codesourcery.com
581 Qinwei qinwei@sunnorth.com.cn
582 Frederic Riss frederic.riss@st.com
583 Aleksandar Ristovski aristovski@qnx.com
584 Tom Rix trix@redhat.com
585 Nick Roberts nickrob@snap.net.nz
586 Bob Rossi bob_rossi@cox.net
587 Theodore A. Roth troth@openavr.org
588 Ian Roxborough irox@redhat.com
589 Maciej W. Rozycki macro@linux-mips.org
590 Grace Sainsbury graces@redhat.com
591 Kei Sakamoto sakamoto.kei@renesas.com
592 Mark Salter msalter@redhat.com
593 Richard Sandiford richard@codesourcery.com
594 Peter Schauer Peter.Schauer@mytum.de
595 Andreas Schwab schwab@linux-m68k.org
596 Thomas Schwinge tschwinge@gnu.org
597 Keith Seitz keiths@redhat.com
598 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
599 Ozkan Sezer sezeroz@gmail.com
600 Stan Shebs stan@codesourcery.com
601 Joel Sherrill joel.sherrill@oarcorp.com
602 Mark Shinwell shinwell@codesourcery.com
603 Craig Silverstein csilvers@google.com
604 Aidan Skinner aidan@velvet.net
605 Jiri Smid smid@suse.cz
606 David Smith dsmith@redhat.com
607 Stephen P. Smith ischis2@cox.net
608 Jackie Smith Cashion jsmith@redhat.com
609 Michael Snyder msnyder@vmware.com
610 Petr Sorfa petrs@caldera.com
611 Andrew Stubbs ams@codesourcery.com
612 Emi Suzuki emi-suzuki@tjsys.co.jp
613 Ian Lance Taylor ian@airs.com
614 Gary Thomas gthomas@redhat.com
615 Jason Thorpe thorpej@netbsd.org
616 Caroline Tice ctice@apple.com
617 Kai Tietz ktietz@redhat.com
618 Andreas Tobler andreast@fgznet.ch
619 Tom Tromey tromey@redhat.com
620 David Ung davidu@mips.com
621 D Venkatasubramanian dvenkat@noida.hcltech.com
622 Corinna Vinschen vinschen@redhat.com
623 Sami Wagiaalla swagiaal@redhat.com
624 Keith Walker keith.walker@arm.com
625 Kris Warkentin kewarken@qnx.com
626 Ulrich Weigand uweigand@de.ibm.com
627 Ken Werner ken.werner@de.ibm.com
628 Nathan Williams nathanw@wasabisystems.com
629 Bob Wilson bob.wilson@acm.org
630 Jim Wilson wilson@tuliptree.org
631 Kwok Cheung Yeung kcy@codesourcery.com
632 Elena Zannoni elena.zannoni@oracle.com
633 Eli Zaretskii eliz@gnu.org
634 Jie Zhang jzhang918@gmail.com
635 Wu Zhou woodzltc@cn.ibm.com
636 Yoshinori Sato ysato@users.sourceforge.jp
637 Hui Zhu teawater@gmail.com
638
639
640 Past Maintainers
641
642 Whenever removing yourself, or someone else, from this file, consider
643 listing their areas of development here for posterity.
644
645 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
646 Jeff Law (hppa) law at cygnus dot com
647 Daniel Berlin (C++ support) dan at cgsoftware dot com
648 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
649 David Taylor (d10v, sparc, utils, defs,
650 expression evaluator, language support) taylor at candd dot org
651 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
652 Frank Ch. Eigler (sim) fche at redhat dot com
653 Per Bothner (Java) per at bothner dot com
654 Anthony Green (Java) green at redhat dot com
655 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
656 Mark Salter (testsuite/lib+config) msalter at redhat dot com
657 Jim Kingdon (web pages) kingdon at panix dot com
658 Jim Ingham (gdbtk, libgui) jingham at apple dot com
659 Mark Kettenis (hurd native) kettenis at gnu dot org
660 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
661 Robert Lipe (SCO/Unixware) rjl at sco dot com
662 Peter Schauer (global, AIX, xcoffsolib,
663 Solaris/x86) Peter.Schauer at mytum dot de
664 Scott Bambrough (ARM) scottb at netwinder dot org
665 Philippe De Muyter (coff) phdm at macqel dot be
666 Michael Chastain (testsuite) mec.gnu at mindspring dot com
667 Fred Fish (global)
668
669
670
671 Folks that have been caught up in a paper trail:
672
673 David Carlton carlton@bactrian.org
674 Ramana Radhakrishnan ramana.r@gmail.com
675
676 ;; Local Variables:
677 ;; coding: utf-8
678 ;; End:
This page took 0.048574 seconds and 4 git commands to generate.