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