Use bfd_get_filename instead of objfile_name in lookup_dwo_unit
[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 Eli Zaretskii
119
120 Global Maintainers
121 ------------------
122
123 The global maintainers may review and commit any change to GDB, except in
124 areas with a Responsible Maintainer available. For major changes, or
125 changes to areas with other active developers, global maintainers are
126 strongly encouraged to post their own patches for feedback before
127 committing.
128
129 The global maintainers are responsible for reviewing patches to any area
130 for which no Responsible Maintainer is listed.
131
132 Global maintainers also have the authority to revert patches which should
133 not have been applied, e.g. patches which were not approved, controversial
134 patches committed under the Obvious Fix Rule, patches with important bugs
135 that can't be immediately fixed, or patches which go against an accepted and
136 documented roadmap for GDB development. Any global maintainer may request
137 the reversion of a patch. If no global maintainer, or responsible
138 maintainer in the affected areas, supports the patch (except for the
139 maintainer who originally committed it), then after 48 hours the maintainer
140 who called for the reversion may revert the patch.
141
142 No one may reapply a reverted patch without the agreement of the maintainer
143 who reverted it, or bringing the issue to the official FSF-appointed
144 GDB maintainers for discussion.
145
146 At the moment there are no documented roadmaps for GDB development; in the
147 future, if there are, a reference to the list will be included here.
148
149 The current global maintainers are (in alphabetical order):
150
151 Pedro Alves palves@redhat.com
152 Joel Brobecker brobecker@adacore.com
153 Kevin Buettner kevinb@redhat.com
154 Andrew Burgess andrew.burgess@embecosm.com
155 Doug Evans dje@google.com
156 Simon Marchi simon.marchi@polymtl.ca
157 Yao Qi qiyao@sourceware.org
158 Tom Tromey tom@tromey.com
159 Tom de Vries tdevries@suse.de
160 Ulrich Weigand Ulrich.Weigand@de.ibm.com
161 Eli Zaretskii eliz@gnu.org
162
163
164 Release Manager
165 ---------------
166
167 The current release manager is: Joel Brobecker <brobecker@adacore.com>
168
169 His responsibilities are:
170
171 * organizing, scheduling, and managing releases of GDB.
172
173 * deciding the approval and commit policies for release branches,
174 and can change them as needed.
175
176
177
178 Patch Champions
179 ---------------
180
181 These volunteers track all patches submitted to the gdb-patches list. They
182 endeavor to prevent any posted patch from being overlooked; work with
183 contributors to meet GDB's coding style and general requirements, along with
184 FSF copyright assignments; remind (ping) responsible maintainers to review
185 patches; and ensure that contributors are given credit.
186
187 Current patch champions (in alphabetical order):
188
189 <none>
190
191
192 Responsible Maintainers
193 -----------------------
194
195 These developers have agreed to review patches in specific areas of GDB, in
196 which they have knowledge and experience. These areas are generally broad;
197 the role of a responsible maintainer is to provide coherent and cohesive
198 structure within their area of GDB, to assure that patches from many
199 different contributors all work together for the best results.
200
201 Global maintainers will defer to responsible maintainers within their areas,
202 as long as the responsible maintainer is active. Active means that
203 responsible maintainers agree to review submitted patches in their area
204 promptly; patches and followups should generally be answered within a week.
205 If a responsible maintainer is interested in reviewing a patch but will not
206 have time within a week of posting, the maintainer should send an
207 acknowledgement of the patch to the gdb-patches mailing list, and
208 plan to follow up with a review within a month. These deadlines are for
209 initial responses to a patch - if the maintainer has suggestions
210 or questions, it may take an extended discussion before the patch
211 is ready to commit. There are no written requirements for discussion,
212 but maintainers are asked to be responsive.
213
214 If a responsible maintainer misses these deadlines occasionally (e.g.
215 vacation or unexpected workload), it's not a disaster - any global
216 maintainer may step in to review the patch. But sometimes life intervenes
217 more permanently, and a maintainer may no longer have time for these duties.
218 When this happens, he or she should step down (either into the Authorized
219 Committers section if still interested in the area, or simply removed from
220 the list of Responsible Maintainers if not).
221
222 If a responsible maintainer is unresponsive for an extended period of time
223 without stepping down, please contact the Global Maintainers; they will try
224 to contact the maintainer directly and fix the problem - potentially by
225 removing that maintainer from their listed position.
226
227 If there are several maintainers for a given domain then any one of them
228 may review a submitted patch.
229
230 Target Instruction Set Architectures:
231
232 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
233 (Operating System / Application Binary Interface) issues including CPU
234 variants.
235
236 The Target/Architecture maintainer works with the host maintainer when
237 resolving build issues. The Target/Architecture maintainer works with
238 the native maintainer when resolving ABI issues.
239
240 aarch64 --target=aarch64-elf ,-Werror
241 Alan Hayward alan.hayward@arm.com
242
243 alpha --target=alpha-elf ,-Werror
244
245 arm --target=arm-elf ,-Werror
246 Alan Hayward alan.hayward@arm.com
247
248 avr --target=avr ,-Werror
249
250 cris --target=cris-elf ,-Werror ,
251 (sim does not build with -Werror)
252
253 frv --target=frv-elf ,-Werror
254
255 h8300 --target=h8300-elf ,-Werror
256
257 i386 --target=i386-elf ,-Werror
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 m68k --target=m68k-elf ,-Werror
270
271 mcore Deleted
272
273 mep --target=mep-elf ,-Werror
274 Kevin Buettner kevinb@redhat.com
275
276 microblaze --target=microblaze-xilinx-elf ,-Werror
277 --target=microblaze-linux-gnu ,-Werror
278 Michael Eager eager@eagercon.com
279
280 mips I-IV --target=mips-elf ,-Werror
281 Maciej W. Rozycki macro@linux-mips.org
282
283 mn10300 --target=mn10300-elf broken
284 (sim/ dies with make -j)
285
286 moxie --target=moxie-elf ,-Werror
287 Anthony Green green@moxielogic.com
288
289 ms1 --target=ms1-elf ,-Werror
290 Kevin Buettner kevinb@redhat.com
291
292 nios2 --target=nios2-elf ,-Werror
293 --target=nios2-linux-gnu ,-Werror
294 Yao Qi qiyao@sourceware.org
295
296 ns32k Deleted
297
298 or1k --target=or1k-elf ,-Werror
299 Stafford Horne shorne@gmail.com
300
301 pa --target=hppa-elf ,-Werror
302
303 powerpc --target=powerpc-eabi ,-Werror
304
305 riscv --target=riscv32-elf ,-Werror
306 --target=riscv64-elf ,-Werror
307 Andrew Burgess andrew.burgess@embecosm.com
308 Palmer Dabbelt palmer@dabbelt.com
309
310 rl78 --target=rl78-elf ,-Werror
311
312 rx --target=rx-elf ,-Werror
313
314 s390 --target=s390-linux-gnu ,-Werror
315 Andreas Arnez arnez@linux.ibm.com
316
317 score --target=score-elf
318 sh --target=sh-elf ,-Werror
319
320 sparc --target=sparcv9-solaris2.11 ,-Werror
321 (--target=sparc-elf broken)
322
323 tic6x --target=tic6x-elf ,-Werror
324 Yao Qi qiyao@sourceware.org
325
326 v850 --target=v850-elf ,-Werror
327
328 vax --target=vax-netbsd ,-Werror
329
330 x86-64 --target=x86_64-linux-gnu ,-Werror
331
332 xstormy16 --target=xstormy16-elf
333 xtensa --target=xtensa-elf
334
335 All developers recognized by this file can make arbitrary changes to
336 OBSOLETE targets.
337
338 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
339 above targets.
340
341
342 Host/Native:
343
344 The Native maintainer is responsible for target specific native
345 support - typically shared libraries and quirks to procfs/ptrace/...
346 The Native maintainer works with the Arch and Core maintainers when
347 resolving more generic problems.
348
349 The host maintainer ensures that gdb can be built as a cross debugger on
350 their platform.
351
352 Darwin Tristan Gingold tgingold@free.fr
353 djgpp native Eli Zaretskii eliz@gnu.org
354 FreeBSD John Baldwin jhb@freebsd.org
355 GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
356 Solaris Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
357
358
359 Core: Generic components used by all of GDB
360
361 linespec Keith Seitz keiths@redhat.com
362
363 language support
364 Ada Joel Brobecker brobecker@adacore.com
365 D Iain Buclaw ibuclaw@gdcproject.org
366 Rust Tom Tromey tom@tromey.com
367 shared libs Kevin Buettner kevinb@redhat.com
368 MI interface Vladimir Prus vladimir@codesourcery.com
369
370 documentation Eli Zaretskii eliz@gnu.org
371 (including NEWS)
372 testsuite
373 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
374
375 SystemTap Sergio Durigan Junior sergiodj@sergiodj.net
376
377
378
379 Reverse debugging / Record and Replay / Tracing:
380
381 record btrace Markus T. Metzger markus.t.metzger@intel.com
382
383
384
385 UI: External (user) interfaces.
386
387 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
388 Keith Seitz keiths@redhat.com
389 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
390
391
392 Misc:
393
394 gdb/gdbserver Daniel Jacobowitz drow@false.org
395
396 Makefile.in, configure* ALL
397
398 mmalloc/ ALL Host maintainers
399
400 sim/ See sim/MAINTAINERS
401
402 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
403 ALL
404 Host maintainers (host dependant parts)
405 (but get your changes into the master version)
406
407 tcl/ tk/ itcl/ ALL
408
409 contrib/ari Pierre Muller muller@sourceware.org
410
411
412 Authorized Committers
413 ---------------------
414
415 These are developers working on particular areas of GDB, who are trusted to
416 commit their own (or other developers') patches in those areas without
417 further review from a Global Maintainer or Responsible Maintainer. They are
418 under no obligation to review posted patches - but, of course, are invited
419 to do so!
420
421 ARM Richard Earnshaw rearnsha@arm.com
422 Blackfin Mike Frysinger vapier@gentoo.org
423 CRIS Hans-Peter Nilsson hp@axis.com
424 IA64 Jeff Johnston jjohnstn@redhat.com
425 MIPS Joel Brobecker brobecker@adacore.com
426 PowerPC Kevin Buettner kevinb@redhat.com
427 S390 Ulrich Weigand uweigand@de.ibm.com
428 djgpp DJ Delorie dj@delorie.com
429 [Please use this address to contact DJ about DJGPP]
430 ia64 Kevin Buettner kevinb@redhat.com
431 AIX Kevin Buettner kevinb@redhat.com
432 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
433 Pascal support Pierre Muller muller@sourceware.org
434
435
436 Write After Approval
437 (alphabetic)
438
439 To get recommended for the Write After Approval list you need a valid
440 FSF assignment and have submitted one good patch.
441
442 Tankut Baris Aktemur tankut.baris.aktemur@intel.com
443 Mihails Strasuns mihails.strasuns@intel.com
444 Pedro Alves pedro_alves@portugalmail.pt
445 David Anderson davea@sgi.com
446 John David Anglin dave.anglin@nrc-cnrc.gc.ca
447 Andreas Arnez arnez@linux.ibm.com
448 Shrinivas Atre shrinivasa@kpitcummins.com
449 Sterling Augustine saugustine@google.com
450 John Baldwin jhb@freebsd.org
451 Scott Bambrough scottb@netwinder.org
452 Marco Barisione mbarisione@undo.io
453 Thiago Jung Bauermann bauerman@br.ibm.com
454 Jon Beniston jon@beniston.com
455 Gary Benson gbenson@redhat.com
456 Gabriel Krisman Bertazi gabriel@krisman.be
457 Jan Beulich jbeulich@novell.com
458 Christian Biesinger cbiesinger@google.com
459 Anton Blanchard anton@samba.org
460 Jim Blandy jimb@codesourcery.com
461 David Blaikie dblaikie@gmail.com
462 Philip Blundell philb@gnu.org
463 Eric Botcazou ebotcazou@libertysurf.fr
464 Per Bothner per@bothner.com
465 Don Breazeal donb@codesourcery.com
466 Joel Brobecker brobecker@adacore.com
467 Dave Brolley brolley@redhat.com
468 Samuel Bronson naesten@gmail.com
469 Paul Brook paul@codesourcery.com
470 Julian Brown julian@codesourcery.com
471 Iain Buclaw ibuclaw@gdcproject.org
472 Kevin Buettner kevinb@redhat.com
473 Andrew Burgess andrew.burgess@embecosm.com
474 David Carlton carlton@bactrian.org
475 Stephane Carrez Stephane.Carrez@gmail.com
476 Michael Chastain mec.gnu@mindspring.com
477 Renquan Cheng crq@gcc.gnu.org
478 Eric Christopher echristo@apple.com
479 Randolph Chung tausq@debian.org
480 Nick Clifton nickc@redhat.com
481 J.T. Conklin jtc@acorntoolworks.com
482 Brendan Conoboy blc@redhat.com
483 Ludovic CourtĂšs ludo@gnu.org
484 Tiago StĂŒrmer Daitx tdaitx@linux.vnet.ibm.com
485 Sanjoy Das sanjoy@playingwithpointers.com
486 Jean-Charles Delay delay@adacore.com
487 DJ Delorie dj@redhat.com
488 Chris Demetriou cgd@google.com
489 Philippe De Muyter phdm@macqel.be
490 Dhananjay Deshpande dhananjayd@kpitcummins.com
491 Markus Deuling deuling@de.ibm.com
492 Klee Dienes kdienes@apple.com
493 Hannes Domani ssbssa@yahoo.de
494 Gabriel Dos Reis gdr@integrable-solutions.net
495 Sergio Durigan Junior sergiodj@sergiodj.net
496 Michael Eager eager@eagercon.com
497 Richard Earnshaw rearnsha@arm.com
498 Bernd Edlinger bernd.edlinger@hotmail.de
499 Steve Ellcey sje@cup.hp.com
500 Frank Ch. Eigler fche@redhat.com
501 Ben Elliston bje@gnu.org
502 Doug Evans dje@google.com
503 Adam Fedor fedor@gnu.org
504 Max Filippov jcmvbkbc@gmail.com
505 Brian Ford ford@vss.fsi.com
506 Matthew Fortune matthew.fortune@imgtec.com
507 Pedro Franco de Carvalho pedromfc@linux.vnet.ibm.com
508 Orjan Friberg orjanf@axis.com
509 Andreas From andreas.from@ericsson.com
510 Nathan Froyd froydnj@codesourcery.com
511 Mike Frysinger vapier@gentoo.org
512 Gary Funck gary@intrepid.com
513 Martin Galvan martingalvan@sourceware.org
514 Chen Gang gang.chen.5i5j@gmail.com
515 Mircea Gherzan mircea.gherzan@intel.com
516 Paul Gilliam pgilliam@us.ibm.com
517 Tristan Gingold tgingold@free.fr
518 Anton Gorenkov xgsa@yandex.ru
519 Raoul Gough RaoulGough@yahoo.co.uk
520 Anthony Green green@redhat.com
521 Matthew Green mrg@eterna.com.au
522 Matthew Gretton-Dann matthew.gretton-dann@arm.com
523 Maxim Grigoriev maxim2405@gmail.com
524 Jerome Guitton guitton@act-europe.fr
525 Ben Harris bjh21@netbsd.org
526 Alan Hayward alan.hayward@arm.com
527 Bernhard Heckel heckel_bernhard@web.de
528 Richard Henderson rth@redhat.com
529 Aldy Hernandez aldyh@redhat.com
530 Paul Hilfinger hilfingr@eecs.berkeley.edu
531 Matt Hiller hiller@redhat.com
532 Kazu Hirata kazu@cs.umass.edu
533 James Hogan james.hogan@imgtec.com
534 Jeff Holcomb jeffh@redhat.com
535 Stafford Horne shorne@gmail.com
536 Don Howard dhoward@redhat.com
537 Nick Hudson nick.hudson@dsl.pipex.com
538 Martin Hunt hunt@redhat.com
539 Meador Inge meadori@codesourcery.com
540 Jim Ingham jingham@apple.com
541 Baurzhan Ismagulov ibr@radix50.net
542 Manoj Iyer manjo@austin.ibm.com
543 Daniel Jacobowitz drow@false.org
544 Andreas Jaeger aj@suse.de
545 Janis Johnson janisjo@codesourcery.com
546 Jeff Johnston jjohnstn@redhat.com
547 Ruslan Kabatsayev b7.10110111@gmail.com
548 Geoff Keating geoffk@redhat.com
549 Mark Kettenis kettenis@gnu.org
550 Marc Khouzam marc.khouzam@ericsson.com
551 Toshihito Kikuchi k.toshihito@yahoo.de
552 Jim Kingdon kingdon@panix.com
553 Anton Kolesov anton.kolesov@synopsys.com
554 Paul Koning paul_koning@dell.com
555 Marcin Koƛcielnicki koriakin@0x04.net
556 Jan Kratochvil jan.kratochvil@redhat.com
557 Maxim Kuvyrkov maxim@kugelworks.com
558 Pierre Langlois pierre.langlois@arm.com
559 Jonathan Larmour jifl@ecoscentric.com
560 Jeff Law law@redhat.com
561 Justin Lebar justin.lebar@gmail.com
562 David Lecomber david@streamline-computing.com
563 Don Lee don.lee@sunplusct.com
564 Yan-Ting Lin currygt52@gmail.com
565 Robert Lipe rjl@sco.com
566 Lei Liu lei.liu2@windriver.com
567 Sandra Loosemore sandra@codesourcery.com
568 Carl Love cel@us.ibm.com
569 H.J. Lu hjl.tools@gmail.com
570 Michal Ludvig mludvig@suse.cz
571 Edjunior B. Machado emachado@linux.vnet.ibm.com
572 Luis Machado luis.machado@linaro.org
573 Jose E. Marchesi jose.marchesi@oracle.com
574 Glen McCready gkm@redhat.com
575 Greg McGary greg@mcgary.org
576 Roland McGrath roland@hack.frob.com
577 Bryce McKinlay mckinlay@redhat.com
578 Jason Merrill jason@redhat.com
579 Markus T. Metzger markus.t.metzger@intel.com
580 David S. Miller davem@redhat.com
581 Mark Mitchell mark@codesourcery.com
582 Marko Mlinar markom@opencores.org
583 Alan Modra amodra@gmail.com
584 Fawzi Mohamed fawzi.mohamed@nokia.com
585 Jason Molenda jmolenda@apple.com
586 Chris Moller cmoller@redhat.com
587 Phil Muldoon pmuldoon@redhat.com
588 Pierre Muller muller@sourceware.org
589 Gaius Mulley gaius@glam.ac.uk
590 Masaki Muranaka monaka@monami-software.com
591 Joseph Myers joseph@codesourcery.com
592 Fernando Nasser fnasser@redhat.com
593 Adam Nemet anemet@caviumnetworks.com
594 Will Newton will.newton@linaro.org
595 Nathanael Nerode neroden@gcc.gnu.org
596 Hans-Peter Nilsson hp@bitrange.com
597 David O'Brien obrien@freebsd.org
598 Alexandre Oliva aoliva@redhat.com
599 Rainer Orth ro@cebitec.uni-bielefeld.de
600 Karen Osmond karen.osmond@gmail.com
601 Pawandeep Oza oza.pawandeep@gmail.com
602 Patrick Palka patrick@parcs.ath.cx
603 Weimin Pan weimin.pan@oracle.com
604 Denis Pilat denis.pilat@st.com
605 Andrew Pinski apinski@cavium.com
606 Kevin Pouget kevin.pouget@st.com
607 Paul Pluzhnikov ppluzhnikov@google.com
608 Marek Polacek mpolacek@redhat.com
609 Siddhesh Poyarekar siddhesh@redhat.com
610 Vladimir Prus vladimir@codesourcery.com
611 Yao Qi qiyao@sourceware.org
612 Qinwei qinwei@sunnorth.com.cn
613 Ramana Radhakrishnan ramana.radhakrishnan@arm.com
614 Siva Chandra Reddy sivachandra@google.com
615 Matt Rice ratmice@gmail.com
616 Frederic Riss frederic.riss@st.com
617 Aleksandar Ristovski aristovski@qnx.com
618 Tom Rix trix@redhat.com
619 Nick Roberts nickrob@snap.net.nz
620 Pierre-Marie de Rodat derodat@adacore.com
621 Xavier Roirand roirand@adacore.com
622 Bob Rossi bob_rossi@cox.net
623 Theodore A. Roth troth@openavr.org
624 Ian Roxborough irox@redhat.com
625 Maciej W. Rozycki macro@linux-mips.org
626 Kamil Rytarowski n54@gmx.com
627 Grace Sainsbury graces@redhat.com
628 Kei Sakamoto sakamoto.kei@renesas.com
629 Mark Salter msalter@redhat.com
630 Richard Sandiford richard@codesourcery.com
631 Iain Sandoe iain@codesourcery.com
632 Peter Schauer Peter.Schauer@mytum.de
633 Andreas Schwab schwab@linux-m68k.org
634 Thomas Schwinge tschwinge@gnu.org
635 Keith Seitz keiths@redhat.com
636 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
637 Ozkan Sezer sezeroz@gmail.com
638 Alok Kumar Sharma AlokKumar.Sharma@amd.com
639 Marcus Shawcroft marcus.shawcroft@arm.com
640 Stan Shebs stanshebs@google.com
641 Joel Sherrill joel.sherrill@oarcorp.com
642 Mark Shinwell shinwell@codesourcery.com
643 Craig Silverstein csilvers@google.com
644 Aidan Skinner aidan@velvet.net
645 Jiri Smid smid@suse.cz
646 Andrey Smirnov andrew.smirnov@gmail.com
647 David Smith dsmith@redhat.com
648 Stephen P. Smith ischis2@cox.net
649 Jackie Smith Cashion jsmith@redhat.com
650 Petr Sorfa petrs@caldera.com
651 Andrew Stubbs ams@codesourcery.com
652 Emi Suzuki emi-suzuki@tjsys.co.jp
653 Alfred M. Szmidt ams@gnu.org
654 Ali Tamur tamur@google.com
655 David Taylor david.taylor@emc.com
656 Ian Lance Taylor ian@airs.com
657 Walfred Tedeschi walfred.tedeschi@intel.com
658 Petr Tesarik ptesarik@suse.cz
659 Gary Thomas gthomas@redhat.com
660 Jason Thorpe thorpej@netbsd.org
661 Caroline Tice ctice@apple.com
662 Kai Tietz ktietz@redhat.com
663 Andreas Tobler andreast@fgznet.ch
664 Jon Turney jon.turney@dronecode.org.uk
665 David Ung davidu@mips.com
666 Shahab Vahedi shahab@synopsys.com
667 D Venkatasubramanian dvenkat@noida.hcltech.com
668 Corinna Vinschen vinschen@redhat.com
669 Jan Vrany jan.vrany@fit.cvut.cz
670 Sami Wagiaalla swagiaal@redhat.com
671 Keith Walker keith.walker@arm.com
672 Ricard Wanderlof ricardw@axis.com
673 Jiong Wang jiong.wang@arm.com
674 Wei-cheng Wang cole945@gmail.com
675 Kris Warkentin kewarken@qnx.com
676 Philippe Waroquiers philippe.waroquiers@skynet.be
677 Ulrich Weigand uweigand@de.ibm.com
678 Ken Werner ken.werner@de.ibm.com
679 Tim Wiederhake tim.wiederhake@intel.com
680 Mark Wielaard mjw@redhat.com
681 Nathan Williams nathanw@wasabisystems.com
682 Bob Wilson bob.wilson@acm.org
683 Jim Wilson wilson@tuliptree.org
684 Andy Wingo wingo@igalia.com
685 Mike Wrighton wrighton@codesourcery.com
686 Kwok Cheung Yeung kcy@codesourcery.com
687 Elena Zannoni ezannoni@gmail.com
688 Eli Zaretskii eliz@gnu.org
689 Jie Zhang jzhang918@gmail.com
690 Wu Zhou woodzltc@cn.ibm.com
691 Yoshinori Sato ysato@users.sourceforge.jp
692 Hui Zhu teawater@gmail.com
693 Khoo Yit Phang khooyp@cs.umd.edu
694
695 Past Maintainers
696
697 Whenever removing yourself, or someone else, from this file, consider
698 listing their areas of development here for posterity.
699
700 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
701 Jeff Law (hppa) law at cygnus dot com
702 Daniel Berlin (C++ support) dan at cgsoftware dot com
703 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
704 David Taylor (d10v, sparc, utils, defs,
705 expression evaluator, language support) taylor at candd dot org
706 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
707 Frank Ch. Eigler (sim) fche at redhat dot com
708 Per Bothner (Java) per at bothner dot com
709 Anthony Green (Java) green at redhat dot com
710 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
711 Mark Salter (testsuite/lib+config) msalter at redhat dot com
712 Jim Kingdon (web pages) kingdon at panix dot com
713 Jim Ingham (gdbtk, libgui) jingham at apple dot com
714 Mark Kettenis (global, i386-elf, m88k-openbsd,
715 GNU/Linux x86, FreeBSD, hurd native, threads) kettenis at gnu dot org
716 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
717 Robert Lipe (SCO/Unixware) rjl at sco dot com
718 Peter Schauer (global, AIX, xcoffsolib,
719 Solaris/x86) Peter.Schauer at mytum dot de
720 Scott Bambrough (ARM) scottb at netwinder dot org
721 Philippe De Muyter (coff) phdm at macqel dot be
722 Michael Chastain (testsuite) mec.gnu at mindspring dot com
723 Fred Fish (global)
724 Jim Blandy (global) jimb@red-bean.com
725 Michael Snyder (global)
726 Christopher Faylor (MS Windows, host & native)
727 Daniel Jacobowitz (global, GNU/Linux MIPS,
728 C++, GDBserver) drow at false dot org
729 Maxim Grigoriev (xtensa) maxim2405 at gmail dot com
730 Andrew Cagney (acting head maintainer,
731 release manager, global, MIPS, PPC, d10v,
732 d30v, sim, mi, multi-arch, unwinder) cagney at gnu dot org
733 Paul Hilfinger (Ada) hilfingr@eecs.berkeley.edu
734 David O'Brien (FreeBSD, host & native) obrien@freebsd.org
735 Jason Thorpe (NetBSD, host & native) thorpej@netbsd.org
736 Gaius Mulley (Modula-2) gaius@glam.ac.uk
737 Kei Sakamoto (m32r) sakamoto.kei@renesas.com
738 Orjan Friberg (CRIS) orjanf@axis.com
739 Qinwei (score-elf) qinwei@sunnorth.com.cn
740 Randolph Chung (HPPA) tausq@debian.org
741 Elena Zannoni (Global, event loop, generic
742 symtabs, DWARF readers, ELF readers, stabs
743 readers, readline) ezannoni@gmail.com
744 Adam Fedor (Objective C) fedor@gnu.org
745 Corinna Vinschen (xstormy16-elf) vinschen@redhat.com
746 Theodore A. Roth (avr) troth@openavr.org
747 Stephane Carrez (m68hc11-elf, tui) Stephane.Carrez@gmail.com
748 Alfred M. Szmidt (GNU Hurd) ams@gnu.org
749 Stan Shebs (Global) stanshebs@google.com
750
751
752 Folks that have been caught up in a paper trail:
753
754 David Carlton carlton@bactrian.org
755
756 ;; Local Variables:
757 ;; coding: utf-8
758 ;; End:
This page took 0.045491 seconds and 4 git commands to generate.