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