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