* MAINTAINERS: Add rl78 to target ISA section.
[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 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 palves@redhat.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 Tom Tromey tromey@redhat.com
170 Ulrich Weigand Ulrich.Weigand@de.ibm.com
171 Elena Zannoni elena.zannoni@oracle.com
172 Eli Zaretskii eliz@gnu.org
173
174
175 Release Manager
176 ---------------
177
178 The current release manager is: Joel Brobecker <brobecker@adacore.com>
179
180 His responsibilities are:
181
182 * organizing, scheduling, and managing releases of GDB.
183
184 * deciding the approval and commit policies for release branches,
185 and can change them as needed.
186
187
188
189 Patch Champions
190 ---------------
191
192 These volunteers track all patches submitted to the gdb-patches list. They
193 endeavor to prevent any posted patch from being overlooked; work with
194 contributors to meet GDB's coding style and general requirements, along with
195 FSF copyright assignments; remind (ping) responsible maintainers to review
196 patches; and ensure that contributors are given credit.
197
198 Current patch champions (in alphabetical order):
199
200 Randolph Chung <tausq@debian.org>
201
202
203
204 Responsible Maintainers
205 -----------------------
206
207 These developers have agreed to review patches in specific areas of GDB, in
208 which they have knowledge and experience. These areas are generally broad;
209 the role of a responsible maintainer is to provide coherent and cohesive
210 structure within their area of GDB, to assure that patches from many
211 different contributors all work together for the best results.
212
213 Global maintainers will defer to responsible maintainers within their areas,
214 as long as the responsible maintainer is active. Active means that
215 responsible maintainers agree to review submitted patches in their area
216 promptly; patches and followups should generally be answered within a week.
217 If a responsible maintainer is interested in reviewing a patch but will not
218 have time within a week of posting, the maintainer should send an
219 acknowledgement of the patch to the gdb-patches mailing list, and
220 plan to follow up with a review within a month. These deadlines are for
221 initial responses to a patch - if the maintainer has suggestions
222 or questions, it may take an extended discussion before the patch
223 is ready to commit. There are no written requirements for discussion,
224 but maintainers are asked to be responsive.
225
226 If a responsible maintainer misses these deadlines occasionally (e.g.
227 vacation or unexpected workload), it's not a disaster - any global
228 maintainer may step in to review the patch. But sometimes life intervenes
229 more permanently, and a maintainer may no longer have time for these duties.
230 When this happens, he or she should step down (either into the Authorized
231 Committers section if still interested in the area, or simply removed from
232 the list of Responsible Maintainers if not).
233
234 If a responsible maintainer is unresponsive for an extended period of time
235 without stepping down, please contact the Global Maintainers; they will try
236 to contact the maintainer directly and fix the problem - potentially by
237 removing that maintainer from their listed position.
238
239 If there are several maintainers for a given domain then any one of them
240 may review a submitted patch.
241
242 Target Instruction Set Architectures:
243
244 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
245 (Operating System / Application Binary Interface) issues including CPU
246 variants.
247
248 The Target/Architecture maintainer works with the host maintainer when
249 resolving build issues. The Target/Architecture maintainer works with
250 the native maintainer when resolving ABI issues.
251
252 alpha --target=alpha-elf ,-Werror
253
254 arm --target=arm-elf ,-Werror
255
256 avr --target=avr ,-Werror
257 Tristan Gingold gingold@adacore.com
258
259 cris --target=cris-elf ,-Werror ,
260 (sim does not build with -Werror)
261
262 frv --target=frv-elf ,-Werror
263
264 h8300 --target=h8300-elf ,-Werror
265
266 i386 --target=i386-elf ,-Werror
267 Mark Kettenis kettenis@gnu.org
268
269 ia64 --target=ia64-linux-gnu ,-Werror
270 (--target=ia64-elf broken)
271
272 lm32 --target=lm32-elf ,-Werror
273
274 m32c --target=m32c-elf ,-Werror
275
276 m32r --target=m32r-elf ,-Werror
277
278 m68hc11 --target=m68hc11-elf ,-Werror ,
279 Stephane Carrez stcarrez@nerim.fr
280
281 m68k --target=m68k-elf ,-Werror
282
283 m88k --target=m88k-openbsd ,-Werror
284 Mark Kettenis kettenis@gnu.org
285
286 mcore Deleted
287
288 mep --target=mep-elf ,-Werror
289 Kevin Buettner kevinb@redhat.com
290
291 microblaze --target=microblaze-xilinx-elf ,-Werror
292 --target=microblaze-linux-gnu ,-Werror
293 Michael Eager eager@eagercon.com
294
295 mips --target=mips-elf ,-Werror
296
297 mn10300 --target=mn10300-elf broken
298 (sim/ dies with make -j)
299
300 moxie --target=moxie-elf ,-Werror
301 Anthony Green green@moxielogic.com
302
303 ms1 --target=ms1-elf ,-Werror
304 Kevin Buettner kevinb@redhat.com
305
306 ns32k Deleted
307
308 pa --target=hppa-elf ,-Werror
309
310 powerpc --target=powerpc-eabi ,-Werror
311
312 rl78 --target=rl78-elf ,-Werror
313
314 s390 --target=s390-linux-gnu ,-Werror
315
316 score --target=score-elf
317 Qinwei qinwei@sunnorth.com.cn
318
319 sh --target=sh-elf ,-Werror
320 --target=sh64-elf ,-Werror
321
322 sparc --target=sparc64-solaris2.10 ,-Werror
323 (--target=sparc-elf broken)
324
325 spu --target=spu-elf ,-Werror
326 Ulrich Weigand uweigand@de.ibm.com
327
328 tic6x --target=tic6x-elf ,-Werror
329 Yao Qi yao@codesourcery.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 drow@false.org
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 threads Mark Kettenis kettenis@gnu.org
378
379 language support
380 Ada Joel Brobecker brobecker@adacore.com
381 Paul Hilfinger hilfinger@gnat.com
382 C++ Daniel Jacobowitz drow@false.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
392
393 UI: External (user) interfaces.
394
395 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
396 Keith Seitz keiths@redhat.com
397 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
398
399
400 Misc:
401
402 gdb/gdbserver Daniel Jacobowitz drow@false.org
403
404 Makefile.in, configure* ALL
405
406 mmalloc/ ALL Host maintainers
407
408 sim/ See sim/MAINTAINERS
409
410 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
411 ALL
412 Host maintainers (host dependant parts)
413 (but get your changes into the master version)
414
415 tcl/ tk/ itcl/ ALL
416
417
418 Authorized Committers
419 ---------------------
420
421 These are developers working on particular areas of GDB, who are trusted to
422 commit their own (or other developers') patches in those areas without
423 further review from a Global Maintainer or Responsible Maintainer. They are
424 under no obligation to review posted patches - but, of course, are invited
425 to do so!
426
427 PowerPC Andrew Cagney cagney@gnu.org
428 ARM Richard Earnshaw rearnsha@arm.com
429 CRIS Hans-Peter Nilsson hp@axis.com
430 IA64 Jeff Johnston jjohnstn@redhat.com
431 MIPS Joel Brobecker brobecker@adacore.com
432 m32r Kei Sakamoto sakamoto.kei@renesas.com
433 PowerPC Kevin Buettner kevinb@redhat.com
434 CRIS Orjan Friberg orjanf@axis.com
435 HPPA Randolph Chung tausq@debian.org
436 S390 Ulrich Weigand uweigand@de.ibm.com
437 djgpp DJ Delorie dj@delorie.com
438 [Please use this address to contact DJ about DJGPP]
439 tui Stephane Carrez stcarrez@nerim.fr
440 ia64 Kevin Buettner kevinb@redhat.com
441 AIX Kevin Buettner kevinb@redhat.com
442 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
443 gdb.java tests Anthony Green green@redhat.com
444 FreeBSD native & host David O'Brien obrien@freebsd.org
445 event loop Elena Zannoni elena.zannoni@oracle.com
446 generic symtabs Elena Zannoni elena.zannoni@oracle.com
447 dwarf readers Elena Zannoni elena.zannoni@oracle.com
448 elf reader Elena Zannoni elena.zannoni@oracle.com
449 stabs reader Elena Zannoni elena.zannoni@oracle.com
450 readline/ Elena Zannoni elena.zannoni@oracle.com
451 NetBSD native & host Jason Thorpe thorpej@netbsd.org
452 Pascal support Pierre Muller muller@sourceware.org
453 avr Theodore A. Roth troth@openavr.org
454 Modula-2 support Gaius Mulley gaius@glam.ac.uk
455
456
457 Write After Approval
458 (alphabetic)
459
460 To get recommended for the Write After Approval list you need a valid
461 FSF assignment and have submitted one good patch.
462
463 Pedro Alves pedro_alves@portugalmail.pt
464 David Anderson davea@sgi.com
465 John David Anglin dave.anglin@nrc-cnrc.gc.ca
466 Shrinivas Atre shrinivasa@kpitcummins.com
467 Sterling Augustine saugustine@google.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 Eric Botcazou ebotcazou@libertysurf.fr
476 Per Bothner per@bothner.com
477 Joel Brobecker brobecker@adacore.com
478 Dave Brolley brolley@redhat.com
479 Paul Brook paul@codesourcery.com
480 Julian Brown julian@codesourcery.com
481 Kevin Buettner kevinb@redhat.com
482 Andrew Burgess aburgess@broadcom.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 Sanjoy Das sanjoy@playingwithpointers.com
495 Jean-Charles Delay delay@adacore.com
496 DJ Delorie dj@redhat.com
497 Chris Demetriou cgd@google.com
498 Philippe De Muyter phdm@macqel.be
499 Dhananjay Deshpande dhananjayd@kpitcummins.com
500 Markus Deuling deuling@de.ibm.com
501 Klee Dienes kdienes@apple.com
502 Gabriel Dos Reis gdr@integrable-solutions.net
503 Sergio Durigan Junior sergiodj@linux.vnet.ibm.com
504 Michael Eager eager@eagercon.com
505 Richard Earnshaw rearnsha@arm.com
506 Steve Ellcey sje@cup.hp.com
507 Frank Ch. Eigler fche@redhat.com
508 Ben Elliston bje@gnu.org
509 Doug Evans dje@google.com
510 Adam Fedor fedor@gnu.org
511 Brian Ford ford@vss.fsi.com
512 Orjan Friberg orjanf@axis.com
513 Nathan Froyd froydnj@codesourcery.com
514 Gary Funck gary@intrepid.com
515 Paul Gilliam pgilliam@us.ibm.com
516 Tristan Gingold gingold@adacore.com
517 Raoul Gough RaoulGough@yahoo.co.uk
518 Anthony Green green@redhat.com
519 Matthew Green mrg@eterna.com.au
520 Matthew Gretton-Dann matthew.gretton-dann@arm.com
521 Maxim Grigoriev maxim2405@gmail.com
522 Jerome Guitton guitton@act-europe.fr
523 Ben Harris bjh21@netbsd.org
524 Richard Henderson rth@redhat.com
525 Aldy Hernandez aldyh@redhat.com
526 Paul Hilfinger hilfinger@gnat.com
527 Matt Hiller hiller@redhat.com
528 Kazu Hirata kazu@cs.umass.edu
529 Jeff Holcomb jeffh@redhat.com
530 Don Howard dhoward@redhat.com
531 Nick Hudson nick.hudson@dsl.pipex.com
532 Martin Hunt hunt@redhat.com
533 Meador Inge meadori@codesourcery.com
534 Jim Ingham jingham@apple.com
535 Baurzhan Ismagulov ibr@radix50.net
536 Manoj Iyer manjo@austin.ibm.com
537 Daniel Jacobowitz drow@false.org
538 Andreas Jaeger aj@suse.de
539 Janis Johnson janisjo@codesourcery.com
540 Jeff Johnston jjohnstn@redhat.com
541 Geoff Keating geoffk@redhat.com
542 Mark Kettenis kettenis@gnu.org
543 Marc Khouzam marc.khouzam@ericsson.com
544 Jim Kingdon kingdon@panix.com
545 Paul Koning paul_koning@dell.com
546 Jan Kratochvil jan.kratochvil@redhat.com
547 Jonathan Larmour jifl@ecoscentric.com
548 Jeff Law law@redhat.com
549 Justin Lebar justin.lebar@gmail.com
550 David Lecomber david@streamline-computing.com
551 Don Lee don.lee@sunplusct.com
552 Robert Lipe rjl@sco.com
553 Sandra Loosemore sandra@codesourcery.com
554 H.J. Lu hjl.tools@gmail.com
555 Michal Ludvig mludvig@suse.cz
556 Edjunior B. Machado emachado@linux.vnet.ibm.com
557 Luis Machado lgustavo@codesourcery.com
558 Glen McCready gkm@redhat.com
559 Greg McGary greg@mcgary.org
560 Roland McGrath roland@redhat.com
561 Bryce McKinlay mckinlay@redhat.com
562 Jason Merrill jason@redhat.com
563 David S. Miller davem@redhat.com
564 Mark Mitchell mark@codesourcery.com
565 Marko Mlinar markom@opencores.org
566 Alan Modra amodra@gmail.com
567 Fawzi Mohamed fawzi.mohamed@nokia.com
568 Jason Molenda jmolenda@apple.com
569 Chris Moller cmoller@redhat.com
570 Phil Muldoon pmuldoon@redhat.com
571 Pierre Muller muller@sourceware.org
572 Gaius Mulley gaius@glam.ac.uk
573 Masaki Muranaka monaka@monami-software.com
574 Joseph Myers joseph@codesourcery.com
575 Fernando Nasser fnasser@redhat.com
576 Adam Nemet anemet@caviumnetworks.com
577 Nathanael Nerode neroden@gcc.gnu.org
578 Hans-Peter Nilsson hp@bitrange.com
579 David O'Brien obrien@freebsd.org
580 Alexandre Oliva aoliva@redhat.com
581 Karen Osmond karen.osmond@gmail.com
582 Denis Pilat denis.pilat@st.com
583 Kevin Pouget kevin.pouget@st.com
584 Paul Pluzhnikov ppluzhnikov@google.com
585 Marek Polacek mpolacek@redhat.com
586 Vladimir Prus vladimir@codesourcery.com
587 Yao Qi yao@codesourcery.com
588 Qinwei qinwei@sunnorth.com.cn
589 Matt Rice ratmice@gmail.com
590 Frederic Riss frederic.riss@st.com
591 Aleksandar Ristovski aristovski@qnx.com
592 Tom Rix trix@redhat.com
593 Nick Roberts nickrob@snap.net.nz
594 Bob Rossi bob_rossi@cox.net
595 Theodore A. Roth troth@openavr.org
596 Ian Roxborough irox@redhat.com
597 Maciej W. Rozycki macro@linux-mips.org
598 Grace Sainsbury graces@redhat.com
599 Kei Sakamoto sakamoto.kei@renesas.com
600 Mark Salter msalter@redhat.com
601 Richard Sandiford richard@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 Nathan Williams nathanw@wasabisystems.com
638 Bob Wilson bob.wilson@acm.org
639 Jim Wilson wilson@tuliptree.org
640 Kwok Cheung Yeung kcy@codesourcery.com
641 Elena Zannoni elena.zannoni@oracle.com
642 Eli Zaretskii eliz@gnu.org
643 Jie Zhang jzhang918@gmail.com
644 Wu Zhou woodzltc@cn.ibm.com
645 Yoshinori Sato ysato@users.sourceforge.jp
646 Hui Zhu teawater@gmail.com
647
648
649 Past Maintainers
650
651 Whenever removing yourself, or someone else, from this file, consider
652 listing their areas of development here for posterity.
653
654 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
655 Jeff Law (hppa) law at cygnus dot com
656 Daniel Berlin (C++ support) dan at cgsoftware dot com
657 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
658 David Taylor (d10v, sparc, utils, defs,
659 expression evaluator, language support) taylor at candd dot org
660 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
661 Frank Ch. Eigler (sim) fche at redhat dot com
662 Per Bothner (Java) per at bothner dot com
663 Anthony Green (Java) green at redhat dot com
664 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
665 Mark Salter (testsuite/lib+config) msalter at redhat dot com
666 Jim Kingdon (web pages) kingdon at panix dot com
667 Jim Ingham (gdbtk, libgui) jingham at apple dot com
668 Mark Kettenis (hurd native) kettenis at gnu dot org
669 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
670 Robert Lipe (SCO/Unixware) rjl at sco dot com
671 Peter Schauer (global, AIX, xcoffsolib,
672 Solaris/x86) Peter.Schauer at mytum dot de
673 Scott Bambrough (ARM) scottb at netwinder dot org
674 Philippe De Muyter (coff) phdm at macqel dot be
675 Michael Chastain (testsuite) mec.gnu at mindspring dot com
676 Fred Fish (global)
677 Jim Blandy (global) jimb@red-bean.com
678 Michael Snyder (global)
679
680
681 Folks that have been caught up in a paper trail:
682
683 David Carlton carlton@bactrian.org
684 Ramana Radhakrishnan ramana.r@gmail.com
685
686 ;; Local Variables:
687 ;; coding: utf-8
688 ;; End:
This page took 0.043611 seconds and 4 git commands to generate.