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