forked from gbenson/binutils-gdb
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathMAINTAINERS
735 lines (586 loc) · 25.9 KB
/
MAINTAINERS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
GDB Maintainers
===============
Overview
--------
This file describes different groups of people who are, together, the
maintainers and developers of the GDB project. Don't worry - it sounds
more complicated than it really is.
There are four groups of GDB developers, covering the patch development and
review process:
- The Global Maintainers.
These are the developers in charge of most daily development. They
have wide authority to apply and reject patches, but defer to the
Responsible Maintainers (see below) within their spheres of
responsibility.
- The Responsible Maintainers.
These are developers who have expertise and interest in a particular
area of GDB, who are generally available to review patches, and who
prefer to enforce a single vision within their areas.
- The Authorized Committers.
These are developers who are trusted to make changes within a specific
area of GDB without additional oversight.
- The Write After Approval Maintainers.
These are developers who have write access to the GDB source tree. They
can check in their own changes once a developer with the appropriate
authority has approved the changes; they can also apply the Obvious
Fix Rule (below).
All maintainers are encouraged to post major patches to the gdb-patches
mailing list for comments, even if they have the authority to commit the
patch without review from another maintainer. This especially includes
patches which change internal interfaces (e.g. global functions, data
structures) or external interfaces (e.g. user, remote, MI, et cetera).
The term "review" is used in this file to describe several kinds of feedback
from a maintainer: approval, rejection, and requests for changes or
clarification with the intention of approving a revised version. Review is
a privilege and/or responsibility of various positions among the GDB
Maintainers. Of course, anyone - whether they hold a position but not the
relevant one for a particular patch, or are just following along on the
mailing lists for fun, or anything in between - may suggest changes or
ask questions about a patch!
There's also a couple of other people who play special roles in the GDB
community, separately from the patch process:
- The Official FSF-appointed GDB Maintainers.
These maintainers are the ones who take the overall responsibility
for GDB, as a package of the GNU project. Other GDB contributors
work under the official maintainers' supervision. They have final
and overriding authority for all GDB-related decisions, including
anything described in this file. As individuals, they may or not
be generally involved in day-to-day development.
- The Release Manager.
This developer is in charge of making new releases of GDB.
- The Patch Champions.
These volunteers make sure that no contribution is overlooked or
forgotten.
Most changes to the list of maintainers in this file are handled by
consensus among the global maintainers and any other involved parties.
In cases where consensus can not be reached, the global maintainers may
ask the official FSF-appointed GDB maintainers for a final decision.
The Obvious Fix Rule
--------------------
All maintainers listed in this file, including the Write After Approval
developers, are allowed to check in obvious fixes.
An "obvious fix" means that there is no possibility that anyone will
disagree with the change.
A good mental test is "will the person who hates my work the most be
able to find fault with the change" - if so, then it's not obvious and
needs to be posted first. :-)
Something like changing or bypassing an interface is _not_ an obvious
fix, since such a change without discussion will result in
instantaneous and loud complaints.
For documentation changes, about the only kind of fix that is obvious
is correction of a typo or bad English usage.
The Official FSF-appointed GDB Maintainers
------------------------------------------
These maintainers as a group have final authority for all GDB-related
topics; they may make whatever changes that they deem necessary, or
that the FSF requests.
The current official FSF-appointed GDB maintainers are listed below,
in alphabetical order. Their affiliations are provided for reference
only - their maintainership status is individual and not through their
affiliation, and they act on behalf of the GNU project.
Pedro Alves (Red Hat)
Joel Brobecker (AdaCore)
Doug Evans (Google)
Eli Zaretskii
Global Maintainers
------------------
The global maintainers may review and commit any change to GDB, except in
areas with a Responsible Maintainer available. For major changes, or
changes to areas with other active developers, global maintainers are
strongly encouraged to post their own patches for feedback before
committing.
The global maintainers are responsible for reviewing patches to any area
for which no Responsible Maintainer is listed.
Global maintainers also have the authority to revert patches which should
not have been applied, e.g. patches which were not approved, controversial
patches committed under the Obvious Fix Rule, patches with important bugs
that can't be immediately fixed, or patches which go against an accepted and
documented roadmap for GDB development. Any global maintainer may request
the reversion of a patch. If no global maintainer, or responsible
maintainer in the affected areas, supports the patch (except for the
maintainer who originally committed it), then after 48 hours the maintainer
who called for the reversion may revert the patch.
No one may reapply a reverted patch without the agreement of the maintainer
who reverted it, or bringing the issue to the official FSF-appointed
GDB maintainers for discussion.
At the moment there are no documented roadmaps for GDB development; in the
future, if there are, a reference to the list will be included here.
The current global maintainers are (in alphabetical order):
Pedro Alves [email protected]
Joel Brobecker [email protected]
Kevin Buettner [email protected]
Andrew Cagney [email protected]
Doug Evans [email protected]
Daniel Jacobowitz [email protected]
Mark Kettenis [email protected]
Yao Qi [email protected]
Stan Shebs [email protected]
Ulrich Weigand [email protected]
Elena Zannoni [email protected]
Eli Zaretskii [email protected]
Release Manager
---------------
The current release manager is: Joel Brobecker <[email protected]>
His responsibilities are:
* organizing, scheduling, and managing releases of GDB.
* deciding the approval and commit policies for release branches,
and can change them as needed.
Patch Champions
---------------
These volunteers track all patches submitted to the gdb-patches list. They
endeavor to prevent any posted patch from being overlooked; work with
contributors to meet GDB's coding style and general requirements, along with
FSF copyright assignments; remind (ping) responsible maintainers to review
patches; and ensure that contributors are given credit.
Current patch champions (in alphabetical order):
Randolph Chung <[email protected]>
Responsible Maintainers
-----------------------
These developers have agreed to review patches in specific areas of GDB, in
which they have knowledge and experience. These areas are generally broad;
the role of a responsible maintainer is to provide coherent and cohesive
structure within their area of GDB, to assure that patches from many
different contributors all work together for the best results.
Global maintainers will defer to responsible maintainers within their areas,
as long as the responsible maintainer is active. Active means that
responsible maintainers agree to review submitted patches in their area
promptly; patches and followups should generally be answered within a week.
If a responsible maintainer is interested in reviewing a patch but will not
have time within a week of posting, the maintainer should send an
acknowledgement of the patch to the gdb-patches mailing list, and
plan to follow up with a review within a month. These deadlines are for
initial responses to a patch - if the maintainer has suggestions
or questions, it may take an extended discussion before the patch
is ready to commit. There are no written requirements for discussion,
but maintainers are asked to be responsive.
If a responsible maintainer misses these deadlines occasionally (e.g.
vacation or unexpected workload), it's not a disaster - any global
maintainer may step in to review the patch. But sometimes life intervenes
more permanently, and a maintainer may no longer have time for these duties.
When this happens, he or she should step down (either into the Authorized
Committers section if still interested in the area, or simply removed from
the list of Responsible Maintainers if not).
If a responsible maintainer is unresponsive for an extended period of time
without stepping down, please contact the Global Maintainers; they will try
to contact the maintainer directly and fix the problem - potentially by
removing that maintainer from their listed position.
If there are several maintainers for a given domain then any one of them
may review a submitted patch.
Target Instruction Set Architectures:
The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
(Operating System / Application Binary Interface) issues including CPU
variants.
The Target/Architecture maintainer works with the host maintainer when
resolving build issues. The Target/Architecture maintainer works with
the native maintainer when resolving ABI issues.
alpha --target=alpha-elf ,-Werror
arm --target=arm-elf ,-Werror
avr --target=avr ,-Werror
cris --target=cris-elf ,-Werror ,
(sim does not build with -Werror)
frv --target=frv-elf ,-Werror
h8300 --target=h8300-elf ,-Werror
i386 --target=i386-elf ,-Werror
Mark Kettenis [email protected]
ia64 --target=ia64-linux-gnu ,-Werror
(--target=ia64-elf broken)
lm32 --target=lm32-elf ,-Werror
m32c --target=m32c-elf ,-Werror
m32r --target=m32r-elf ,-Werror
m68hc11 --target=m68hc11-elf ,-Werror ,
Stephane Carrez [email protected]
m68k --target=m68k-elf ,-Werror
m88k --target=m88k-openbsd ,-Werror
Mark Kettenis [email protected]
mcore Deleted
mep --target=mep-elf ,-Werror
Kevin Buettner [email protected]
microblaze --target=microblaze-xilinx-elf ,-Werror
--target=microblaze-linux-gnu ,-Werror
Michael Eager [email protected]
mips --target=mips-elf ,-Werror
Maciej W. Rozycki [email protected]
mn10300 --target=mn10300-elf broken
(sim/ dies with make -j)
moxie --target=moxie-elf ,-Werror
Anthony Green [email protected]
ms1 --target=ms1-elf ,-Werror
Kevin Buettner [email protected]
nios2 --target=nios2-elf ,-Werror
--target=nios2-linux-gnu ,-Werror
Yao Qi [email protected]
ns32k Deleted
pa --target=hppa-elf ,-Werror
powerpc --target=powerpc-eabi ,-Werror
rl78 --target=rl78-elf ,-Werror
rx --target=rx-elf ,-Werror
s390 --target=s390-linux-gnu ,-Werror
score --target=score-elf
Qinwei [email protected]
sh --target=sh-elf ,-Werror
--target=sh64-elf ,-Werror
sparc --target=sparc64-solaris2.10 ,-Werror
(--target=sparc-elf broken)
spu --target=spu-elf ,-Werror
Ulrich Weigand [email protected]
tic6x --target=tic6x-elf ,-Werror
Yao Qi [email protected]
v850 --target=v850-elf ,-Werror
vax --target=vax-netbsd ,-Werror
x86-64 --target=x86_64-linux-gnu ,-Werror
xstormy16 --target=xstormy16-elf
Corinna Vinschen [email protected]
xtensa --target=xtensa-elf
Maxim Grigoriev [email protected]
All developers recognized by this file can make arbitrary changes to
OBSOLETE targets.
The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
above targets.
Host/Native:
The Native maintainer is responsible for target specific native
support - typically shared libraries and quirks to procfs/ptrace/...
The Native maintainer works with the Arch and Core maintainers when
resolving more generic problems.
The host maintainer ensures that gdb can be built as a cross debugger on
their platform.
AIX Joel Brobecker [email protected]
Darwin Tristan Gingold [email protected]
djgpp native Eli Zaretskii [email protected]
GNU Hurd Alfred M. Szmidt [email protected]
GNU/Linux/x86 native & host
Mark Kettenis [email protected]
GNU/Linux MIPS native & host
Daniel Jacobowitz [email protected]
GNU/Linux m68k Andreas Schwab [email protected]
FreeBSD native & host Mark Kettenis [email protected]
Core: Generic components used by all of GDB
threads Mark Kettenis [email protected]
language support
Ada Joel Brobecker [email protected]
Paul Hilfinger [email protected]
C++ Daniel Jacobowitz [email protected]
Objective C support Adam Fedor [email protected]
shared libs Kevin Buettner [email protected]
MI interface Vladimir Prus [email protected]
documentation Eli Zaretskii [email protected]
(including NEWS)
testsuite
gdbtk (gdb.gdbtk) Keith Seitz [email protected]
SystemTap Sergio Durigan Junior [email protected]
Reverse debugging / Record and Replay / Tracing:
record btrace Markus T. Metzger [email protected]
UI: External (user) interfaces.
gdbtk (c & tcl) Fernando Nasser [email protected]
Keith Seitz [email protected]
libgui (w/foundry, sn) Keith Seitz [email protected]
Misc:
gdb/gdbserver Daniel Jacobowitz [email protected]
Makefile.in, configure* ALL
mmalloc/ ALL Host maintainers
sim/ See sim/MAINTAINERS
readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
ALL
Host maintainers (host dependant parts)
(but get your changes into the master version)
tcl/ tk/ itcl/ ALL
contrib/ari Pierre Muller [email protected]
Authorized Committers
---------------------
These are developers working on particular areas of GDB, who are trusted to
commit their own (or other developers') patches in those areas without
further review from a Global Maintainer or Responsible Maintainer. They are
under no obligation to review posted patches - but, of course, are invited
to do so!
PowerPC Andrew Cagney [email protected]
ARM Richard Earnshaw [email protected]
Blackfin Mike Frysinger [email protected]
CRIS Hans-Peter Nilsson [email protected]
IA64 Jeff Johnston [email protected]
MIPS Joel Brobecker [email protected]
m32r Kei Sakamoto [email protected]
PowerPC Kevin Buettner [email protected]
CRIS Orjan Friberg [email protected]
HPPA Randolph Chung [email protected]
S390 Ulrich Weigand [email protected]
djgpp DJ Delorie [email protected]
[Please use this address to contact DJ about DJGPP]
tui Stephane Carrez [email protected]
ia64 Kevin Buettner [email protected]
AIX Kevin Buettner [email protected]
GNU/Linux PPC native Kevin Buettner [email protected]
gdb.java tests Anthony Green [email protected]
FreeBSD native & host David O'Brien [email protected]
event loop Elena Zannoni [email protected]
generic symtabs Elena Zannoni [email protected]
dwarf readers Elena Zannoni [email protected]
elf reader Elena Zannoni [email protected]
stabs reader Elena Zannoni [email protected]
readline/ Elena Zannoni [email protected]
NetBSD native & host Jason Thorpe [email protected]
Pascal support Pierre Muller [email protected]
avr Theodore A. Roth [email protected]
Modula-2 support Gaius Mulley [email protected]
Write After Approval
(alphabetic)
To get recommended for the Write After Approval list you need a valid
FSF assignment and have submitted one good patch.
Pedro Alves [email protected]
David Anderson [email protected]
John David Anglin [email protected]
Shrinivas Atre [email protected]
Sterling Augustine [email protected]
John Baldwin [email protected]
Scott Bambrough [email protected]
Thiago Jung Bauermann [email protected]
Jon Beniston [email protected]
Gary Benson [email protected]
Gabriel Krisman Bertazi [email protected]
Jan Beulich [email protected]
Anton Blanchard [email protected]
Jim Blandy [email protected]
David Blaikie [email protected]
Philip Blundell [email protected]
Eric Botcazou [email protected]
Per Bothner [email protected]
Don Breazeal [email protected]
Joel Brobecker [email protected]
Dave Brolley [email protected]
Samuel Bronson [email protected]
Paul Brook [email protected]
Julian Brown [email protected]
Iain Buclaw [email protected]
Kevin Buettner [email protected]
Andrew Burgess [email protected]
Andrew Cagney [email protected]
David Carlton [email protected]
Stephane Carrez [email protected]
Michael Chastain [email protected]
Renquan Cheng [email protected]
Eric Christopher [email protected]
Randolph Chung [email protected]
Nick Clifton [email protected]
J.T. Conklin [email protected]
Brendan Conoboy [email protected]
Ludovic Courtès [email protected]
Tiago Stürmer Daitx [email protected]
Sanjoy Das [email protected]
Jean-Charles Delay [email protected]
DJ Delorie [email protected]
Chris Demetriou [email protected]
Philippe De Muyter [email protected]
Dhananjay Deshpande [email protected]
Markus Deuling [email protected]
Klee Dienes [email protected]
Gabriel Dos Reis [email protected]
Sergio Durigan Junior [email protected]
Michael Eager [email protected]
Richard Earnshaw [email protected]
Steve Ellcey [email protected]
Frank Ch. Eigler [email protected]
Ben Elliston [email protected]
Doug Evans [email protected]
Adam Fedor [email protected]
Max Filippov [email protected]
Brian Ford [email protected]
Matthew Fortune [email protected]
Orjan Friberg [email protected]
Andreas From [email protected]
Nathan Froyd [email protected]
Mike Frysinger [email protected]
Gary Funck [email protected]
Martin Galvan [email protected]
Chen Gang [email protected]
Mircea Gherzan [email protected]
Paul Gilliam [email protected]
Tristan Gingold [email protected]
Anton Gorenkov [email protected]
Raoul Gough [email protected]
Anthony Green [email protected]
Matthew Green [email protected]
Matthew Gretton-Dann [email protected]
Maxim Grigoriev [email protected]
Jerome Guitton [email protected]
Ben Harris [email protected]
Richard Henderson [email protected]
Aldy Hernandez [email protected]
Paul Hilfinger [email protected]
Matt Hiller [email protected]
Kazu Hirata [email protected]
James Hogan [email protected]
Jeff Holcomb [email protected]
Don Howard [email protected]
Nick Hudson [email protected]
Martin Hunt [email protected]
Meador Inge [email protected]
Jim Ingham [email protected]
Baurzhan Ismagulov [email protected]
Manoj Iyer [email protected]
Daniel Jacobowitz [email protected]
Andreas Jaeger [email protected]
Janis Johnson [email protected]
Jeff Johnston [email protected]
Geoff Keating [email protected]
Mark Kettenis [email protected]
Marc Khouzam [email protected]
Jim Kingdon [email protected]
Paul Koning [email protected]
Jan Kratochvil [email protected]
Maxim Kuvyrkov [email protected]
Pierre Langlois [email protected]
Jonathan Larmour [email protected]
Jeff Law [email protected]
Justin Lebar [email protected]
David Lecomber [email protected]
Don Lee [email protected]
Robert Lipe [email protected]
Lei Liu [email protected]
Sandra Loosemore [email protected]
H.J. Lu [email protected]
Michal Ludvig [email protected]
Edjunior B. Machado [email protected]
Luis Machado [email protected]
Jose E. Marchesi [email protected]
Simon Marchi [email protected]
Glen McCready [email protected]
Greg McGary [email protected]
Roland McGrath [email protected]
Bryce McKinlay [email protected]
Jason Merrill [email protected]
Markus T. Metzger [email protected]
David S. Miller [email protected]
Mark Mitchell [email protected]
Marko Mlinar [email protected]
Alan Modra [email protected]
Fawzi Mohamed [email protected]
Jason Molenda [email protected]
Chris Moller [email protected]
Phil Muldoon [email protected]
Pierre Muller [email protected]
Gaius Mulley [email protected]
Masaki Muranaka [email protected]
Joseph Myers [email protected]
Fernando Nasser [email protected]
Adam Nemet [email protected]
Will Newton [email protected]
Nathanael Nerode [email protected]
Hans-Peter Nilsson [email protected]
David O'Brien [email protected]
Alexandre Oliva [email protected]
Karen Osmond [email protected]
Pawandeep Oza [email protected]
Patrick Palka [email protected]
Denis Pilat [email protected]
Andrew Pinski [email protected]
Kevin Pouget [email protected]
Paul Pluzhnikov [email protected]
Marek Polacek [email protected]
Siddhesh Poyarekar [email protected]
Vladimir Prus [email protected]
Yao Qi [email protected]
Qinwei [email protected]
Ramana Radhakrishnan [email protected]
Siva Chandra Reddy [email protected]
Matt Rice [email protected]
Frederic Riss [email protected]
Aleksandar Ristovski [email protected]
Tom Rix [email protected]
Nick Roberts [email protected]
Pierre-Marie de Rodat [email protected]
Bob Rossi [email protected]
Theodore A. Roth [email protected]
Ian Roxborough [email protected]
Maciej W. Rozycki [email protected]
Grace Sainsbury [email protected]
Kei Sakamoto [email protected]
Mark Salter [email protected]
Richard Sandiford [email protected]
Iain Sandoe [email protected]
Peter Schauer [email protected]
Andreas Schwab [email protected]
Thomas Schwinge [email protected]
Keith Seitz [email protected]
Carlos Eduardo Seo [email protected]
Ozkan Sezer [email protected]
Marcus Shawcroft [email protected]
Stan Shebs [email protected]
Joel Sherrill [email protected]
Mark Shinwell [email protected]
Craig Silverstein [email protected]
Aidan Skinner [email protected]
Jiri Smid [email protected]
Andrey Smirnov [email protected]
David Smith [email protected]
Stephen P. Smith [email protected]
Jackie Smith Cashion [email protected]
Petr Sorfa [email protected]
Andrew Stubbs [email protected]
Emi Suzuki [email protected]
Ian Lance Taylor [email protected]
Walfred Tedeschi [email protected]
Gary Thomas [email protected]
Jason Thorpe [email protected]
Caroline Tice [email protected]
Kai Tietz [email protected]
Andreas Tobler [email protected]
Antoine Tremblay [email protected]
Jon Turney [email protected]
David Ung [email protected]
D Venkatasubramanian [email protected]
Corinna Vinschen [email protected]
Sami Wagiaalla [email protected]
Keith Walker [email protected]
Ricard Wanderlof [email protected]
Jiong Wang [email protected]
Wei-cheng Wang [email protected]
Kris Warkentin [email protected]
Philippe Waroquiers [email protected]
Ulrich Weigand [email protected]
Ken Werner [email protected]
Mark Wielaard [email protected]
Nathan Williams [email protected]
Bob Wilson [email protected]
Jim Wilson [email protected]
Andy Wingo [email protected]
Mike Wrighton [email protected]
Kwok Cheung Yeung [email protected]
Elena Zannoni [email protected]
Eli Zaretskii [email protected]
Jie Zhang [email protected]
Wu Zhou [email protected]
Yoshinori Sato [email protected]
Hui Zhu [email protected]
Khoo Yit Phang [email protected]
Past Maintainers
Whenever removing yourself, or someone else, from this file, consider
listing their areas of development here for posterity.
Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
Jeff Law (hppa) law at cygnus dot com
Daniel Berlin (C++ support) dan at cgsoftware dot com
Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
David Taylor (d10v, sparc, utils, defs,
expression evaluator, language support) taylor at candd dot org
J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
Frank Ch. Eigler (sim) fche at redhat dot com
Per Bothner (Java) per at bothner dot com
Anthony Green (Java) green at redhat dot com
Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
Mark Salter (testsuite/lib+config) msalter at redhat dot com
Jim Kingdon (web pages) kingdon at panix dot com
Jim Ingham (gdbtk, libgui) jingham at apple dot com
Mark Kettenis (hurd native) kettenis at gnu dot org
Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
Robert Lipe (SCO/Unixware) rjl at sco dot com
Peter Schauer (global, AIX, xcoffsolib,
Solaris/x86) Peter.Schauer at mytum dot de
Scott Bambrough (ARM) scottb at netwinder dot org
Philippe De Muyter (coff) phdm at macqel dot be
Michael Chastain (testsuite) mec.gnu at mindspring dot com
Fred Fish (global)
Jim Blandy (global) [email protected]
Michael Snyder (global)
Christopher Faylor (MS Windows, host & native)
Folks that have been caught up in a paper trail:
David Carlton [email protected]
;; Local Variables:
;; coding: utf-8
;; End: