| blob | 9c44ec977f54811a67a599867e395a940404702a |
1 GDB Maintainers
2 ===============
5 Overview
6 --------
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.
12 There are four groups of GDB developers, covering the patch development and
13 review process:
15 - The Global Maintainers.
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.
22 - The Responsible Maintainers.
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.
28 - The Authorized Committers.
30 These are developers who are trusted to make changes within a specific
31 area of GDB without additional oversight.
33 - The Write After Approval Maintainers.
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).
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).
46 The word "contributor" is used in this document to refer to any GDB
47 developer listed above as well as folks who may have suggested some
48 patches but aren't part of one of those categories for any reason.
50 There's also a couple of other people who play special roles in the GDB
51 community, separately from the patch process:
53 - The Official FSF-appointed GDB Maintainers.
55 These maintainers are the ones who take the overall responsibility
56 for GDB, as a package of the GNU project. Other GDB contributors
57 work under the official maintainers' supervision. They have final
58 and overriding authority for all GDB-related decisions, including
59 anything described in this file. As individuals, they may or not
60 be generally involved in day-to-day development.
62 - The Release Manager.
64 This developer is in charge of making new releases of GDB.
66 - The Patch Champions.
68 These volunteers make sure that no contribution is overlooked or
69 forgotten.
71 Most changes to the list of maintainers in this file are handled by
72 consensus among the global maintainers and any other involved parties.
73 In cases where consensus can not be reached, the global maintainers may
74 ask the official FSF-appointed GDB maintainers for a final decision.
76 The term "review" is used in this file to describe several kinds of
77 feedback from a maintainer: approval, rejection, and requests for changes
78 or clarification with the intention of approving a revised version.
79 Approval is a privilege and/or responsibility of various positions among
80 the GDB Maintainers. Of course, anyone - whether they hold a position, but
81 not the relevant one for a particular patch, or are just following along on
82 the mailing lists for fun, or anything in between - may suggest changes, ask
83 questions about a patch or say if they believe a patch is fit for upstreaming!
85 To ensure that patches are only pushed when approved, and to properly credit
86 the contributors who take the time to improve this project, the following
87 trailers are used to identify who contributed and how. The trailers (or tags)
88 currently in use are:
90 - Tested-By:
92 Used when a contributor has tested the patch and finds that it
93 fixes the claimed problem. It may also be used to indicate that
94 the contributor has performed regression testing. By itself, this
95 tag says nothing about the quality of the fix implemented by the
96 patch, nor the amount of testing that was actually performed.
98 Usage: "Tested-By: Your Name <your@email>"
100 - Acked-By:
102 Used when a responsible or global maintainer has taken a superficial
103 look at a patch and agrees with its direction, but has not done further
104 review on the subject.
105 This trailer can be specific to one or more areas of the project, as
106 defined by the "Responsible maintainers" section of this file. If
107 that is the case, the area(s) should be added at the end of the tag in
108 parenthesis in a comma-separated list.
110 Usage: "Acked-By: Your Name <your@email> (area1, area2)"
112 - Reviewed-By:
114 Used when a contributor has looked at the code and agrees with
115 the changes, but either doesn't have the authority or doesn't
116 feel comfortable approving the patch.
117 This trailer can be specific to one or more areas of the project, as
118 defined by the "Responsible maintainers" section of this file. If
119 that is the case, the area(s) should be added at the end of the tag in
120 parenthesis in a comma-separated list.
122 Usage: "Reviewed-By: Your Name <your@email> (area1, area2)"
124 - Approved-By:
126 Used by responsible maintainers or global maintainers when a patch is
127 ready to be upstreamed. If a patch requires multiple approvals, only
128 the last reviewer should use this tag, making it obvious to the
129 contributor that the patch is ready to be pushed.
130 This trailer can be specific to one or more areas of the project, as
131 defined by the "Responsible maintainers" section of this file. If
132 that is the case, the area(s) should be added at the end of the tag in
133 parenthesis in a comma separated list. Patches must have all areas
134 approved before being pushed. If a patch has had some areas approved,
135 it is recommended that the final approver makes it explicit that the
136 patch is ready for pushing.
137 Responsible, Global and Official FSF-appointed maintainers may approve
138 their own patches, but it is recommended that they seek external approval
139 before doing so.
141 Usage: "Approved-By: Your Name <your@email>"
143 - Co-Authored-By:
145 Used when the commit includes meaningful contributions from multiple people.
147 Usage: "Co-Authored-By: Contributor's Name <their@email>"
149 - Bug:
151 This trailer is added with a link to the GDB bug tracker bug for
152 added context on relevant commits.
154 Usage: "Bug: <link>"
156 Sometimes, contributors may request small changes, such as fixing typos, before
157 granting the review or approval trailer. When the contributor thinks that
158 these changes are so small that it isn't necessary to send a new version, they
159 may add some text like "with these changes, I'm ok with the patch", followed by
160 their trailer. In those situations, the trailer is only valid after the
161 changes are made.
164 The Obvious Fix Rule
165 --------------------
167 All maintainers listed in this file, including the Write After Approval
168 developers, are allowed to check in obvious fixes.
170 An "obvious fix" means that there is no possibility that anyone will
171 disagree with the change.
173 A good mental test is "will the person who hates my work the most be
174 able to find fault with the change" - if so, then it's not obvious and
175 needs to be posted first. :-)
177 Something like changing or bypassing an interface is _not_ an obvious
178 fix, since such a change without discussion will result in
179 instantaneous and loud complaints.
181 For documentation changes, about the only kind of fix that is obvious
182 is correction of a typo or bad English usage.
185 The Official FSF-appointed GDB Maintainers
186 ------------------------------------------
188 These maintainers as a group have final authority for all GDB-related
189 topics; they may make whatever changes that they deem necessary, or
190 that the FSF requests.
192 The current official FSF-appointed GDB maintainers are listed below,
193 in alphabetical order. Their affiliations are provided for reference
194 only - their maintainership status is individual and not through their
195 affiliation, and they act on behalf of the GNU project.
197 Pedro Alves
198 Joel Brobecker (AdaCore)
199 Doug Evans (Google)
200 Eli Zaretskii
202 Global Maintainers
203 ------------------
205 The global maintainers may review and commit any change to GDB, except in
206 areas with a Responsible Maintainer available. For major changes, or
207 changes to areas with other active developers, global maintainers are
208 strongly encouraged to post their own patches for feedback before
209 committing.
211 The global maintainers are responsible for reviewing patches to any area
212 for which no Responsible Maintainer is listed.
214 Global maintainers also have the authority to revert patches which should
215 not have been applied, e.g. patches which were not approved, controversial
216 patches committed under the Obvious Fix Rule, patches with important bugs
217 that can't be immediately fixed, or patches which go against an accepted and
218 documented roadmap for GDB development. Any global maintainer may request
219 the reversion of a patch. If no global maintainer, or responsible
220 maintainer in the affected areas, supports the patch (except for the
221 maintainer who originally committed it), then after 48 hours the maintainer
222 who called for the reversion may revert the patch.
224 No one may reapply a reverted patch without the agreement of the maintainer
225 who reverted it, or bringing the issue to the official FSF-appointed
226 GDB maintainers for discussion.
228 At the moment there are no documented roadmaps for GDB development; in the
229 future, if there are, a reference to the list will be included here.
231 The current global maintainers are (in alphabetical order):
233 Pedro Alves pedro@palves.net
234 John Baldwin jhb@freebsd.org
235 Kevin Buettner kevinb@redhat.com
236 Andrew Burgess aburgess@redhat.com
237 Luis Machado luis.machado@arm.com
238 Simon Marchi simon.marchi@polymtl.ca
239 Tom Tromey tom@tromey.com
240 Tom de Vries tdevries@suse.de
241 Ulrich Weigand Ulrich.Weigand@de.ibm.com
242 Eli Zaretskii eliz@gnu.org
245 Release Manager
246 ---------------
248 The current release manager is: Joel Brobecker <brobecker@adacore.com>
250 His responsibilities are:
252 * organizing, scheduling, and managing releases of GDB.
254 * deciding the approval and commit policies for release branches,
255 and can change them as needed.
259 Patch Champions
260 ---------------
262 These volunteers track all patches submitted to the gdb-patches list. They
263 endeavor to prevent any posted patch from being overlooked; work with
264 contributors to meet GDB's coding style and general requirements, along with
265 FSF copyright assignments; remind (ping) responsible maintainers to review
266 patches; and ensure that contributors are given credit.
268 Current patch champions (in alphabetical order):
270 <none>
273 Responsible Maintainers
274 -----------------------
276 These developers have agreed to review patches in specific areas of GDB, in
277 which they have knowledge and experience. These areas are generally broad;
278 the role of a responsible maintainer is to provide coherent and cohesive
279 structure within their area of GDB, to assure that patches from many
280 different contributors all work together for the best results.
282 Global maintainers will defer to responsible maintainers within their areas,
283 as long as the responsible maintainer is active. Active means that
284 responsible maintainers agree to review submitted patches in their area
285 promptly; patches and followups should generally be answered within a week.
286 If a responsible maintainer is interested in reviewing a patch but will not
287 have time within a week of posting, the maintainer should send an
288 acknowledgement of the patch to the gdb-patches mailing list, and
289 plan to follow up with a review within a month. These deadlines are for
290 initial responses to a patch - if the maintainer has suggestions
291 or questions, it may take an extended discussion before the patch
292 is ready to commit. There are no written requirements for discussion,
293 but maintainers are asked to be responsive.
295 If a responsible maintainer misses these deadlines occasionally (e.g.
296 vacation or unexpected workload), it's not a disaster - any global
297 maintainer may step in to review the patch. But sometimes life intervenes
298 more permanently, and a maintainer may no longer have time for these duties.
299 When this happens, he or she should step down (either into the Authorized
300 Committers section if still interested in the area, or simply removed from
301 the list of Responsible Maintainers if not).
303 If a responsible maintainer is unresponsive for an extended period of time
304 without stepping down, please contact the Global Maintainers; they will try
305 to contact the maintainer directly and fix the problem - potentially by
306 removing that maintainer from their listed position.
308 If there are several maintainers for a given domain then any one of them
309 may review a submitted patch.
311 Target Instruction Set Architectures:
313 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
314 (Operating System / Application Binary Interface) issues including CPU
315 variants.
317 The Target/Architecture maintainer works with the host maintainer when
318 resolving build issues. The Target/Architecture maintainer works with
319 the native maintainer when resolving ABI issues.
321 aarch64 --target=aarch64-elf
322 Alan Hayward alan.hayward@arm.com
323 Luis Machado luis.machado@arm.com
325 alpha --target=alpha-elf
327 amdgpu --target=amdgcn*-*-*
328 Lancelot Six lancelot.six@amd.com
330 arc --target=arc-elf
331 Shahab Vahedi shahab@synopsys.com
333 arm --target=arm-elf
334 Alan Hayward alan.hayward@arm.com
335 Luis Machado luis.machado@arm.com
337 avr --target=avr
339 bpf --target=bpf-unknown-none
340 Jose E. Marchesi jose.marchesi@oracle.com
342 cris --target=cris-elf
344 frv --target=frv-elf
346 h8300 --target=h8300-elf
348 i386 --target=i386-elf
350 ia64 --target=ia64-linux-gnu
351 (--target=ia64-elf broken)
353 lm32 --target=lm32-elf
355 loongarch --target=loongarch32-elf
356 --target=loongarch64-elf
357 Tiezhu Yang yangtiezhu@loongson.cn
359 m32c --target=m32c-elf
361 m32r --target=m32r-elf
363 m68hc11 --target=m68hc11-elf
364 m68k --target=m68k-elf
366 mcore Deleted
368 mep --target=mep-elf
369 Kevin Buettner kevinb@redhat.com
371 microblaze --target=microblaze-xilinx-elf
372 --target=microblaze-linux-gnu
373 Michael Eager eager@eagercon.com
375 mips I-IV --target=mips-elf
376 Maciej W. Rozycki macro@orcam.me.uk
378 mn10300 --target=mn10300-elf broken
379 (sim/ dies with make -j)
381 moxie --target=moxie-elf
382 Anthony Green green@moxielogic.com
384 ms1 Deleted
386 nios2 --target=nios2-elf
387 --target=nios2-linux-gnu
388 Yao Qi qiyao@sourceware.org
390 ns32k Deleted
392 or1k --target=or1k-elf
393 Stafford Horne shorne@gmail.com
395 pa --target=hppa-elf
397 powerpc --target=powerpc-eabi
399 riscv --target=riscv32-elf
400 --target=riscv64-elf
401 Andrew Burgess aburgess@redhat.com
402 Palmer Dabbelt palmer@dabbelt.com
404 rl78 --target=rl78-elf
406 rx --target=rx-elf
408 s390 --target=s390-linux-gnu
409 Andreas Arnez arnez@linux.ibm.com
411 sh --target=sh-elf
413 sparc --target=sparcv9-solaris2.11
414 (--target=sparc-elf broken)
416 tic6x --target=tic6x-elf
417 Yao Qi qiyao@sourceware.org
419 v850 --target=v850-elf
421 vax --target=vax-netbsd
423 x86-64 --target=x86_64-linux-gnu
425 xstormy16 --target=xstormy16-elf
426 xtensa --target=xtensa-elf
428 All developers recognized by this file can make arbitrary changes to
429 OBSOLETE targets.
431 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
432 above targets.
435 Host/Native:
437 The Native maintainer is responsible for target specific native
438 support - typically shared libraries and quirks to procfs/ptrace/...
439 The Native maintainer works with the Arch and Core maintainers when
440 resolving more generic problems.
442 The host maintainer ensures that gdb can be built as a cross debugger on
443 their platform.
445 Darwin Tristan Gingold tgingold@free.fr
446 djgpp native Eli Zaretskii eliz@gnu.org
447 FreeBSD John Baldwin jhb@freebsd.org
448 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
449 Solaris Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
452 Core: Generic components used by all of GDB
454 linespec Keith Seitz keiths@redhat.com
456 language support
457 D Iain Buclaw ibuclaw@gdcproject.org
458 Rust Tom Tromey tom@tromey.com
459 shared libs Kevin Buettner kevinb@redhat.com
460 MI interface Vladimir Prus vladimir@codesourcery.com
462 documentation Eli Zaretskii eliz@gnu.org
463 (including NEWS)
464 testsuite
465 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
467 SystemTap Sergio Durigan Junior sergiodj@sergiodj.net
471 Reverse debugging / Record and Replay / Tracing:
473 record
474 full Guinevere Larsen blarsen@redhat.com
475 btrace Markus T. Metzger markus.t.metzger@intel.com
479 UI: External (user) interfaces.
481 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
482 Keith Seitz keiths@redhat.com
483 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
486 Misc:
488 gdb/gdbserver Daniel Jacobowitz drow@false.org
490 Makefile.in, configure* ALL
492 mmalloc/ ALL Host maintainers
494 sim/ See sim/MAINTAINERS
496 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
497 ALL
498 Host maintainers (host dependant parts)
499 (but get your changes into the master version)
501 tcl/ tk/ itcl/ ALL
503 contrib/ari Pierre Muller muller@sourceware.org
506 Authorized Committers
507 ---------------------
509 These are developers working on particular areas of GDB, who are trusted to
510 commit their own (or other developers') patches in those areas without
511 further review from a Global Maintainer or Responsible Maintainer. They are
512 under no obligation to review posted patches - but, of course, are invited
513 to do so!
515 ARM Richard Earnshaw rearnsha@arm.com
516 Blackfin Mike Frysinger vapier@gentoo.org
517 CRIS Hans-Peter Nilsson hp@axis.com
518 IA64 Jeff Johnston jjohnstn@redhat.com
519 PowerPC Kevin Buettner kevinb@redhat.com
520 S390 Ulrich Weigand uweigand@de.ibm.com
521 djgpp DJ Delorie dj@delorie.com
522 [Please use this address to contact DJ about DJGPP]
523 ia64 Kevin Buettner kevinb@redhat.com
524 AIX Kevin Buettner kevinb@redhat.com
525 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
526 Pascal support Pierre Muller muller@sourceware.org
529 Write After Approval
530 (alphabetic)
532 To get recommended for the Write After Approval list you need a valid
533 FSF assignment and have submitted one good patch.
535 Tankut Baris Aktemur tankut.baris.aktemur@intel.com
536 David Anderson davea@sgi.com
537 John David Anglin dave.anglin@nrc-cnrc.gc.ca
538 Andreas Arnez arnez@linux.ibm.com
539 Shrinivas Atre shrinivasa@kpitcummins.com
540 Sterling Augustine saugustine@google.com
541 Scott Bambrough scottb@netwinder.org
542 Marco Barisione mbarisione@undo.io
543 Thiago Jung Bauermann thiago.bauermann@linaro.org
544 Jon Beniston jon@beniston.com
545 Gary Benson gbenson@redhat.com
546 Gabriel Krisman Bertazi gabriel@krisman.be
547 Jan Beulich jbeulich@novell.com
548 Christian Biesinger cbiesinger@google.com
549 Anton Blanchard anton@samba.org
550 Jim Blandy jimb@codesourcery.com
551 David Blaikie dblaikie@gmail.com
552 Philip Blundell philb@gnu.org
553 Eric Botcazou ebotcazou@libertysurf.fr
554 Per Bothner per@bothner.com
555 Don Breazeal donb@codesourcery.com
556 Joel Brobecker brobecker@adacore.com
557 Dave Brolley brolley@redhat.com
558 Samuel Bronson naesten@gmail.com
559 Paul Brook paul@codesourcery.com
560 Julian Brown julian@codesourcery.com
561 Iain Buclaw ibuclaw@gdcproject.org
562 Kevin Buettner kevinb@redhat.com
563 Richard Bunt richard.bunt@linaro.org
564 Andrew Burgess aburgess@redhat.com
565 David Carlton carlton@bactrian.org
566 Stephane Carrez Stephane.Carrez@gmail.com
567 Michael Chastain mec.gnu@mindspring.com
568 Renquan Cheng crq@gcc.gnu.org
569 Eric Christopher echristo@apple.com
570 Randolph Chung tausq@debian.org
571 Nick Clifton nickc@redhat.com
572 J.T. Conklin jtc@acorntoolworks.com
573 Brendan Conoboy blc@redhat.com
574 Ludovic Courtès ludo@gnu.org
575 Tiago Stürmer Daitx tdaitx@linux.vnet.ibm.com
576 Sanjoy Das sanjoy@playingwithpointers.com
577 Jean-Charles Delay delay@adacore.com
578 DJ Delorie dj@redhat.com
579 Chris Demetriou cgd@google.com
580 Philippe De Muyter phdm@macqel.be
581 Dhananjay Deshpande dhananjayd@kpitcummins.com
582 Markus Deuling deuling@de.ibm.com
583 Klee Dienes kdienes@apple.com
584 Hannes Domani ssbssa@yahoo.de
585 Gabriel Dos Reis gdr@integrable-solutions.net
586 Sergio Durigan Junior sergiodj@sergiodj.net
587 Michael Eager eager@eagercon.com
588 Richard Earnshaw rearnsha@arm.com
589 Bernd Edlinger bernd.edlinger@hotmail.de
590 Steve Ellcey sje@cup.hp.com
591 Frank Ch. Eigler fche@redhat.com
592 Ben Elliston bje@gnu.org
593 Doug Evans dje@google.com
594 Simon Farre simon.farre.cx@gmail.com
595 Adam Fedor fedor@gnu.org
596 Max Filippov jcmvbkbc@gmail.com
597 Brian Ford ford@vss.fsi.com
598 Matthew Fortune matthew.fortune@imgtec.com
599 Pedro Franco de Carvalho pedromfc@linux.vnet.ibm.com
600 Orjan Friberg orjanf@axis.com
601 Andreas From andreas.from@ericsson.com
602 Nathan Froyd froydnj@codesourcery.com
603 Mike Frysinger vapier@gentoo.org
604 Gary Funck gary@intrepid.com
605 Martin Galvan martingalvan@sourceware.org
606 Chen Gang gang.chen.5i5j@gmail.com
607 Mircea Gherzan mircea.gherzan@intel.com
608 Paul Gilliam pgilliam@us.ibm.com
609 Tristan Gingold tgingold@free.fr
610 Anton Gorenkov xgsa@yandex.ru
611 Raoul Gough RaoulGough@yahoo.co.uk
612 Anthony Green green@redhat.com
613 Matthew Green mrg@eterna.com.au
614 Matthew Gretton-Dann matthew.gretton-dann@arm.com
615 Maxim Grigoriev maxim2405@gmail.com
616 Jerome Guitton guitton@act-europe.fr
617 Alexandra Hájková ahajkova@redhat.com
618 Ben Harris bjh21@netbsd.org
619 Alan Hayward alan.hayward@arm.com
620 Bernhard Heckel heckel_bernhard@web.de
621 Richard Henderson rth@redhat.com
622 Aldy Hernandez aldyh@redhat.com
623 Paul Hilfinger hilfingr@eecs.berkeley.edu
624 Matt Hiller hiller@redhat.com
625 Kazu Hirata kazu@cs.umass.edu
626 James Hogan james.hogan@imgtec.com
627 Jeff Holcomb jeffh@redhat.com
628 Stafford Horne shorne@gmail.com
629 Magne Hov mhov@undo.io
630 Don Howard dhoward@redhat.com
631 Nick Hudson nick.hudson@dsl.pipex.com
632 Martin Hunt hunt@redhat.com
633 Abdul Basit Ijaz abdul.b.ijaz@intel.com
634 Meador Inge meadori@codesourcery.com
635 Jim Ingham jingham@apple.com
636 Baurzhan Ismagulov ibr@radix50.net
637 Manoj Iyer manjo@austin.ibm.com
638 Daniel Jacobowitz drow@false.org
639 Andreas Jaeger aj@suse.de
640 Sam James sam@gentoo.org
641 Janis Johnson janisjo@codesourcery.com
642 Jeff Johnston jjohnstn@redhat.com
643 Ruslan Kabatsayev b7.10110111@gmail.com
644 Geoff Keating geoffk@redhat.com
645 Nils-Christian Kempke nils-christian.kempke@intel.com
646 Mark Kettenis kettenis@gnu.org
647 Marc Khouzam marc.khouzam@ericsson.com
648 Toshihito Kikuchi k.toshihito@yahoo.de
649 Jim Kingdon kingdon@panix.com
650 Anton Kolesov anton.kolesov@synopsys.com
651 Paul Koning paul_koning@dell.com
652 Marcin Kościelnicki koriakin@0x04.net
653 Jan Kratochvil jan.kratochvil@redhat.com
654 Maxim Kuvyrkov maxim@kugelworks.com
655 Pierre Langlois pierre.langlois@arm.com
656 Jonathan Larmour jifl@ecoscentric.com
657 Guinevere Larsen blarsen@redhat.com
658 Jeff Law law@redhat.com
659 Justin Lebar justin.lebar@gmail.com
660 David Lecomber david@streamline-computing.com
661 Don Lee don.lee@sunplusct.com
662 Kévin Le Gouguec legouguec@adacore.com
663 Enze Li enze.li@hotmail.com
664 Yan-Ting Lin currygt52@gmail.com
665 Robert Lipe rjl@sco.com
666 Lei Liu lei.liu2@windriver.com
667 Yang Liu liuyang22@iscas.ac.cn
668 Sandra Loosemore sandra@codesourcery.com
669 Carl Love cel@linux.ibm.com
670 H.J. Lu hjl.tools@gmail.com
671 Michal Ludvig mludvig@suse.cz
672 Edjunior B. Machado emachado@linux.vnet.ibm.com
673 Jose E. Marchesi jose.marchesi@oracle.com
674 Glen McCready gkm@redhat.com
675 Greg McGary greg@mcgary.org
676 Roland McGrath roland@hack.frob.com
677 Bryce McKinlay mckinlay@redhat.com
678 Jason Merrill jason@redhat.com
679 Markus T. Metzger markus.t.metzger@intel.com
680 David S. Miller davem@redhat.com
681 Mark Mitchell mark@codesourcery.com
682 Marko Mlinar markom@opencores.org
683 Alan Modra amodra@gmail.com
684 Fawzi Mohamed fawzi.mohamed@nokia.com
685 Jason Molenda jmolenda@apple.com
686 Chris Moller cmoller@redhat.com
687 Patrick Monnerat patrick@monnerat.net
688 Phil Muldoon pmuldoon@redhat.com
689 Pierre Muller muller@sourceware.org
690 Gaius Mulley gaius@glam.ac.uk
691 Masaki Muranaka monaka@monami-software.com
692 Joseph Myers josmyers@redhat.com
693 Fernando Nasser fnasser@redhat.com
694 Adam Nemet anemet@caviumnetworks.com
695 Will Newton will.newton@linaro.org
696 Nathanael Nerode neroden@gcc.gnu.org
697 Hans-Peter Nilsson hp@bitrange.com
698 David O'Brien obrien@freebsd.org
699 Tsukasa Oi research_trasio@irq.a4lg.com
700 Alexandre Oliva aoliva@redhat.com
701 Rainer Orth ro@cebitec.uni-bielefeld.de
702 Karen Osmond karen.osmond@gmail.com
703 Pawandeep Oza oza.pawandeep@gmail.com
704 Patrick Palka patrick@parcs.ath.cx
705 Weimin Pan weimin.pan@oracle.com
706 Denis Pilat denis.pilat@st.com
707 Andrew Pinski apinski@cavium.com
708 Kevin Pouget kevin.pouget@st.com
709 Paul Pluzhnikov ppluzhnikov@google.com
710 Marek Polacek mpolacek@redhat.com
711 Siddhesh Poyarekar siddhesh@redhat.com
712 Vladimir Prus vladimir@codesourcery.com
713 Yao Qi qiyao@sourceware.org
714 Qinwei qinwei@sunnorth.com.cn
715 Ramana Radhakrishnan ramana.radhakrishnan@arm.com
716 Siva Chandra Reddy sivachandra@google.com
717 Matt Rice ratmice@gmail.com
718 Frederic Riss frederic.riss@st.com
719 Aleksandar Ristovski aristovski@qnx.com
720 Tom Rix trix@redhat.com
721 Nick Roberts nickrob@snap.net.nz
722 Pierre-Marie de Rodat derodat@adacore.com
723 Xavier Roirand roirand@adacore.com
724 Bob Rossi bob_rossi@cox.net
725 Theodore A. Roth troth@openavr.org
726 Yvan Roux yvan.roux@foss.st.com
727 Ian Roxborough irox@redhat.com
728 Maciej W. Rozycki macro@orcam.me.uk
729 Kamil Rytarowski n54@gmx.com
730 Grace Sainsbury graces@redhat.com
731 Kei Sakamoto sakamoto.kei@renesas.com
732 Mark Salter msalter@redhat.com
733 Richard Sandiford richard@codesourcery.com
734 Iain Sandoe iain@codesourcery.com
735 Peter Schauer Peter.Schauer@mytum.de
736 Will Schmidt will_schmidt@vnet.ibm.com
737 Andreas Schwab schwab@linux-m68k.org
738 Thomas Schwinge tschwinge@gnu.org
739 Keith Seitz keiths@redhat.com
740 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
741 Ozkan Sezer sezeroz@gmail.com
742 Alok Kumar Sharma AlokKumar.Sharma@amd.com
743 Marcus Shawcroft marcus.shawcroft@arm.com
744 Stan Shebs stanshebs@google.com
745 Joel Sherrill joel.sherrill@oarcorp.com
746 Mark Shinwell shinwell@codesourcery.com
747 Craig Silverstein csilvers@google.com
748 Lancelot Six lsix@lancelotsix.com
749 Aidan Skinner aidan@velvet.net
750 Jiri Smid smid@suse.cz
751 Andrey Smirnov andrew.smirnov@gmail.com
752 David Smith dsmith@redhat.com
753 Stephen P. Smith ischis2@cox.net
754 Jackie Smith Cashion jsmith@redhat.com
755 Petr Sorfa petrs@caldera.com
756 Mihails Strasuns mihails.strasuns@intel.com
757 Andrew Stubbs ams@codesourcery.com
758 Emi Suzuki emi-suzuki@tjsys.co.jp
759 Torbjörn Svensson torbjorn.svensson@foss.st.com
760 Alfred M. Szmidt ams@gnu.org
761 Ali Tamur tamur@google.com
762 David Taylor david.taylor@emc.com
763 Ian Lance Taylor ian@airs.com
764 Walfred Tedeschi walfred.tedeschi@intel.com
765 Petr Tesarik petr@tesarici.cz
766 Samuel Thibault samuel.thibault@ens-lyon.org
767 Gary Thomas gthomas@redhat.com
768 Jason Thorpe thorpej@netbsd.org
769 Caroline Tice ctice@apple.com
770 Kai Tietz ktietz@redhat.com
771 Andreas Tobler andreast@fgznet.ch
772 Jon Turney jon.turney@dronecode.org.uk
773 David Ung davidu@mips.com
774 Shahab Vahedi shahab@synopsys.com
775 D Venkatasubramanian dvenkat@noida.hcltech.com
776 Corinna Vinschen vinschen@redhat.com
777 Jan Vrany jan.vrany@fit.cvut.cz
778 Sami Wagiaalla swagiaal@redhat.com
779 Keith Walker keith.walker@arm.com
780 Ricard Wanderlof ricardw@axis.com
781 Jiong Wang jiong.wang@arm.com
782 Wei-cheng Wang cole945@gmail.com
783 Kris Warkentin kewarken@qnx.com
784 Philippe Waroquiers philippe.waroquiers@skynet.be
785 Ulrich Weigand uweigand@de.ibm.com
786 Ken Werner ken.werner@de.ibm.com
787 Tim Wiederhake tim.wiederhake@intel.com
788 Mark Wielaard mark@klomp.org
789 Felix Willgerodt felix.willgerodt@intel.com
790 Nathan Williams nathanw@wasabisystems.com
791 Bob Wilson bob.wilson@acm.org
792 Jim Wilson wilson@tuliptree.org
793 Andy Wingo wingo@igalia.com
794 Ciaran Woodward ciaranwoodward@xmos.com
795 Mike Wrighton wrighton@codesourcery.com
796 Tiezhu Yang yangtiezhu@loongson.cn
797 Kwok Cheung Yeung kcy@codesourcery.com
798 Elena Zannoni ezannoni@gmail.com
799 Eli Zaretskii eliz@gnu.org
800 Jie Zhang jzhang918@gmail.com
801 Wu Zhou woodzltc@cn.ibm.com
802 Yoshinori Sato ysato@users.sourceforge.jp
803 Hui Zhu teawater@gmail.com
804 Khoo Yit Phang khooyp@cs.umd.edu
805 Rogerio Alves rcardoso@linux.ibm.com
807 Past Maintainers
809 Whenever removing yourself, or someone else, from this file, consider
810 listing their areas of development here for posterity.
812 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
813 Jeff Law (hppa) law at cygnus dot com
814 Daniel Berlin (C++ support) dan at cgsoftware dot com
815 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
816 David Taylor (d10v, sparc, utils, defs,
817 expression evaluator, language support) taylor at candd dot org
818 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
819 Frank Ch. Eigler (sim) fche at redhat dot com
820 Per Bothner (Java) per at bothner dot com
821 Anthony Green (Java) green at redhat dot com
822 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
823 Mark Salter (testsuite/lib+config) msalter at redhat dot com
824 Jim Kingdon (web pages) kingdon at panix dot com
825 Jim Ingham (gdbtk, libgui) jingham at apple dot com
826 Mark Kettenis (global, i386-elf, m88k-openbsd,
827 GNU/Linux x86, FreeBSD, hurd native, threads) kettenis at gnu dot org
828 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
829 Robert Lipe (SCO/Unixware) rjl at sco dot com
830 Peter Schauer (global, AIX, xcoffsolib,
831 Solaris/x86) Peter.Schauer at mytum dot de
832 Scott Bambrough (ARM) scottb at netwinder dot org
833 Philippe De Muyter (coff) phdm at macqel dot be
834 Michael Chastain (testsuite) mec.gnu at mindspring dot com
835 Fred Fish (global)
836 Jim Blandy (global) jimb@red-bean.com
837 Michael Snyder (global)
838 Christopher Faylor (MS Windows, host & native)
839 Daniel Jacobowitz (global, GNU/Linux MIPS,
840 C++, GDBserver) drow at false dot org
841 Maxim Grigoriev (xtensa) maxim2405 at gmail dot com
842 Andrew Cagney (acting head maintainer,
843 release manager, global, MIPS, PPC, d10v,
844 d30v, sim, mi, multi-arch, unwinder) cagney at gnu dot org
845 Paul Hilfinger (Ada) hilfingr@eecs.berkeley.edu
846 David O'Brien (FreeBSD, host & native) obrien@freebsd.org
847 Jason Thorpe (NetBSD, host & native) thorpej@netbsd.org
848 Gaius Mulley (Modula-2) gaius@glam.ac.uk
849 Kei Sakamoto (m32r) sakamoto.kei@renesas.com
850 Orjan Friberg (CRIS) orjanf@axis.com
851 Qinwei (score-elf) qinwei@sunnorth.com.cn
852 Randolph Chung (HPPA) tausq@debian.org
853 Elena Zannoni (Global, event loop, generic
854 symtabs, DWARF readers, ELF readers, stabs
855 readers, readline) ezannoni@gmail.com
856 Adam Fedor (Objective C) fedor@gnu.org
857 Corinna Vinschen (xstormy16-elf) vinschen@redhat.com
858 Theodore A. Roth (avr) troth@openavr.org
859 Stephane Carrez (m68hc11-elf, tui) Stephane.Carrez@gmail.com
860 Alfred M. Szmidt (GNU Hurd) ams@gnu.org
861 Stan Shebs (Global) stanshebs@google.com
862 Joel Brobecker (Global, Ada) brobecker@adacore.com
863 Doug Evans (Global) dje@google.com
864 Yao Qi (Global) qiyao@sourceware.org
867 Folks that have been caught up in a paper trail:
869 David Carlton carlton@bactrian.org
871 ;; Local Variables:
872 ;; coding: utf-8
873 ;; End: