Commit | Line | Data |
---|---|---|
e990a46e | 1 | GDB Maintainers |
b2a74f99 DJ |
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 GDB Steering Committee. | |
59 | ||
60 | These are the official (FSF-appointed) maintainers of GDB. They have | |
61 | final and overriding authority for all GDB-related decisions, including | |
62 | anything described in this file. The committee is not generally | |
63 | involved in day-to-day development (although its members may be, as | |
64 | individuals). | |
65 | ||
66 | - The Release Manager. | |
67 | ||
68 | This developer is in charge of making new releases of GDB. | |
69 | ||
70 | - The Patch Champions. | |
71 | ||
72 | These volunteers make sure that no contribution is overlooked or | |
73 | forgotten. | |
74 | ||
75 | Most changes to the list of maintainers in this file are handled by | |
76 | consensus among the global maintainers and any other involved parties. | |
77 | In cases where consensus can not be reached, the global maintainers may | |
78 | ask the Steering Committee for a final decision. | |
79 | ||
80 | ||
81 | The Obvious Fix Rule | |
82 | -------------------- | |
83 | ||
84 | All maintainers listed in this file, including the Write After Approval | |
85 | developers, are allowed to check in obvious fixes. | |
86 | ||
87 | An "obvious fix" means that there is no possibility that anyone will | |
88 | disagree with the change. | |
89 | ||
90 | A good mental test is "will the person who hates my work the most be | |
91 | able to find fault with the change" - if so, then it's not obvious and | |
92 | needs to be posted first. :-) | |
93 | ||
94 | Something like changing or bypassing an interface is _not_ an obvious | |
95 | fix, since such a change without discussion will result in | |
96 | instantaneous and loud complaints. | |
97 | ||
e990a46e AC |
98 | |
99 | GDB Steering Committee | |
b2a74f99 | 100 | ---------------------- |
e990a46e AC |
101 | |
102 | The members of the GDB Steering Committee are the FSF-appointed | |
103 | maintainers of the GDB project. | |
104 | ||
b2a74f99 DJ |
105 | The Steering Committee has final authority for all GDB-related topics; |
106 | they may make whatever changes that they deem necessary, or that the FSF | |
107 | requests. However, they are generally not involved in day-to-day | |
108 | development. | |
109 | ||
110 | The current members of the steering committee are listed below, in | |
111 | alphabetical order. Their affiliations are provided for reference only - | |
112 | their membership on the Steering Committee is individual and not through | |
113 | their affiliation, and they act on behalf of the GNU project. | |
114 | ||
2f83030f | 115 | Jim Blandy (CodeSourcery) |
e990a46e AC |
116 | Andrew Cagney (Red Hat) |
117 | Robert Dewar (AdaCore, NYU) | |
118 | Klee Dienes (Apple) | |
119 | Paul Hilfinger (UC Berkeley) | |
120 | Dan Jacobowitz (CodeSourcery) | |
121 | Stan Shebs (Apple) | |
122 | Richard Stallman (FSF) | |
123 | Ian Lance Taylor (C2) | |
124 | Todd Whitesel | |
ef7b4488 | 125 | |
5185fdd7 | 126 | |
b2a74f99 DJ |
127 | Global Maintainers |
128 | ------------------ | |
129 | ||
130 | The global maintainers may review and commit any change to GDB, except in | |
131 | areas with a Responsible Maintainer available. For major changes, or | |
132 | changes to areas with other active developers, global maintainers are | |
133 | strongly encouraged to post their own patches for feedback before | |
134 | committing. | |
135 | ||
136 | The global maintainers are responsible for reviewing patches to any area | |
137 | for which no Responsible Maintainer is listed. | |
138 | ||
139 | Global maintainers also have the authority to revert patches which should | |
140 | not have been applied, e.g. patches which were not approved, controversial | |
141 | patches committed under the Obvious Fix Rule, patches with important bugs | |
142 | that can't be immediately fixed, or patches which go against an accepted and | |
143 | documented roadmap for GDB development. Any global maintainer may request | |
144 | the reversion of a patch. If no global maintainer, or responsible | |
145 | maintainer in the affected areas, supports the patch (except for the | |
146 | maintainer who originally committed it), then after 48 hours the maintainer | |
147 | who called for the reversion may revert the patch. | |
148 | ||
149 | No one may reapply a reverted patch without the agreement of the maintainer | |
150 | who reverted it, or bringing the issue to the GDB Steering Committee for | |
151 | discussion. | |
152 | ||
153 | At the moment there are no documented roadmaps for GDB development; in the | |
154 | future, if there are, a reference to the list will be included here. | |
155 | ||
156 | The current global maintainers are (in alphabetical order): | |
5185fdd7 | 157 | |
2f83030f | 158 | Jim Blandy jimb@codesourcery.com |
904507ce | 159 | Kevin Buettner kevinb@redhat.com |
1db2a798 | 160 | Andrew Cagney cagney@gnu.org |
abdcb2a5 | 161 | Fred Fish fnf@ninemoons.com |
0ec30a36 | 162 | Daniel Jacobowitz dan@debian.org |
1b57acd2 | 163 | Mark Kettenis kettenis@gnu.org |
e7411eaa | 164 | Stan Shebs shebs@apple.com |
f9e2d830 | 165 | Michael Snyder msnyder@redhat.com |
904507ce AC |
166 | Elena Zannoni ezannoni@redhat.com |
167 | Eli Zaretskii eliz@gnu.org | |
5185fdd7 | 168 | |
f5bca8e7 | 169 | |
b2a74f99 DJ |
170 | Release Manager |
171 | --------------- | |
5185fdd7 | 172 | |
b2a74f99 | 173 | The current release manager is: Joel Brobecker <brobecker@adacore.com> |
5185fdd7 | 174 | |
b2a74f99 | 175 | His responsibilities are: |
36c2118f | 176 | |
b2a74f99 | 177 | * organizing, scheduling, and managing releases of GDB. |
538aae9d | 178 | |
b2a74f99 DJ |
179 | * deciding the approval and commit policies for release branches, |
180 | and can change them as needed. | |
5185fdd7 | 181 | |
58cfabe6 | 182 | |
58cfabe6 | 183 | |
b2a74f99 DJ |
184 | Patch Champions |
185 | --------------- | |
58cfabe6 | 186 | |
b2a74f99 DJ |
187 | These volunteers track all patches submitted to the gdb-patches list. They |
188 | endeavor to prevent any posted patch from being overlooked; work with | |
189 | contributors to meet GDB's coding style and general requirements, along with | |
190 | FSF copyright assignments; remind (ping) responsible maintainers to review | |
191 | patches; and ensure that contributors are given credit. | |
58cfabe6 | 192 | |
b2a74f99 | 193 | Current patch champions (in alphabetical order): |
54c92070 | 194 | |
c9f7217e | 195 | Randolph Chung <tausq@debian.org> |
b2a74f99 | 196 | Daniel Jacobowitz <dan@debian.org> |
58cfabe6 | 197 | |
a60a53c5 | 198 | |
a60a53c5 | 199 | |
b2a74f99 DJ |
200 | Responsible Maintainers |
201 | ----------------------- | |
202 | ||
203 | These developers have agreed to review patches in specific areas of GDB, in | |
204 | which they have knowledge and experience. These areas are generally broad; | |
205 | the role of a responsible maintainer is to provide coherent and cohesive | |
206 | structure within their area of GDB, to assure that patches from many | |
207 | different contributors all work together for the best results. | |
a60a53c5 | 208 | |
b2a74f99 DJ |
209 | Global maintainers will defer to responsible maintainers within their areas, |
210 | as long as the responsible maintainer is active. Active means that | |
211 | responsible maintainers agree to review submitted patches in their area | |
212 | promptly; patches and followups should generally be answered within a week. | |
213 | If a responsible maintainer is interested in reviewing a patch but will not | |
214 | have time within a week of posting, the maintainer should send an | |
215 | acknowledgement of the patch to the gdb-patches mailing list, and | |
216 | plan to follow up with a review within a month. These deadlines are for | |
217 | initial responses to a patch - if the maintainer has suggestions | |
218 | or questions, it may take an extended discussion before the patch | |
219 | is ready to commit. There are no written requirements for discussion, | |
220 | but maintainers are asked to be responsive. | |
221 | ||
222 | If a responsible maintainer misses these deadlines occasionally (e.g. | |
223 | vacation or unexpected workload), it's not a disaster - any global | |
224 | maintainer may step in to review the patch. But sometimes life intervenes | |
225 | more permanently, and a maintainer may no longer have time for these duties. | |
226 | When this happens, he or she should step down (either into the Authorized | |
227 | Committers section if still interested in the area, or simply removed from | |
228 | the list of Responsible Maintainers if not). | |
229 | ||
230 | If a responsible maintainer is unresponsive for an extended period of time | |
231 | without stepping down, please contact the Global Maintainers; they will try | |
232 | to contact the maintainer directly and fix the problem - potentially by | |
233 | removing that maintainer from their listed position. | |
234 | ||
235 | If there are several maintainers for a given domain then any one of them | |
236 | may review a submitted patch. | |
a60a53c5 | 237 | |
c1bab85b | 238 | Target Instruction Set Architectures: |
8860ff2e | 239 | |
91a533d4 AC |
240 | The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI |
241 | (Operating System / Application Binary Interface) issues including CPU | |
242 | variants. | |
243 | ||
244 | The Target/Architecture maintainer works with the host maintainer when | |
245 | resolving build issues. The Target/Architecture maintainer works with | |
246 | the native maintainer when resolving ABI issues. | |
5185fdd7 | 247 | |
8f9cbe01 | 248 | alpha --target=alpha-elf ,-Werror |
21a6f6bb | 249 | |
66140c26 | 250 | arm --target=arm-elf ,-Werror |
26806ce2 | 251 | Richard Earnshaw rearnsha@arm.com |
9b82661c | 252 | |
e33ce519 | 253 | avr --target=avr ,-Werror |
e33ce519 | 254 | |
4a72630a | 255 | cris --target=cris-elf ,-Werror |
93755ae6 | 256 | |
61c82a3b | 257 | d10v OBSOLETE |
21a6f6bb | 258 | |
53e8aaea | 259 | frv --target=frv-elf ,-Werror |
53e8aaea | 260 | |
87d088f5 | 261 | h8300 --target=h8300-elf ,-Werror |
9b82661c | 262 | |
c1bab85b | 263 | i386 --target=i386-elf ,-Werror |
21a6f6bb AC |
264 | Mark Kettenis kettenis@gnu.org |
265 | ||
32089c7c AC |
266 | ia64 --target=ia64-linux-gnu ,-Werror |
267 | (--target=ia64-elf broken) | |
9b82661c | 268 | |
96309189 MS |
269 | m32c --target=m32c-elf ,-Werror |
270 | Jim Blandy, jimb@codesourcery.com | |
271 | ||
9644bbdd | 272 | m32r --target=m32r-elf ,-Werror |
9b82661c | 273 | |
53fe9346 | 274 | m68hc11 --target=m68hc11-elf ,-Werror , |
2be99286 | 275 | Stephane Carrez stcarrez@nerim.fr |
9b82661c | 276 | |
043c9cdc | 277 | m68k --target=m68k-elf ,-Werror |
9b82661c | 278 | |
1698f4e7 MK |
279 | m88k --target=m88k-openbsd ,-Werror |
280 | Mark Kettenis kettenis@gnu.org | |
9b82661c | 281 | |
9445aa30 | 282 | mcore Deleted |
9b82661c | 283 | |
c1bab85b | 284 | mips --target=mips-elf ,-Werror |
9b82661c | 285 | |
87d088f5 AC |
286 | mn10300 --target=mn10300-elf broken |
287 | (sim/ dies with make -j) | |
5260ca71 | 288 | Michael Snyder msnyder@redhat.com |
9b82661c | 289 | |
37ebea84 KB |
290 | ms1 --target=ms1-elf ,-Werror |
291 | Kevin Buettner kevinb@redhat.com | |
292 | ||
9445aa30 | 293 | ns32k Deleted |
9b82661c | 294 | |
93449403 | 295 | pa --target=hppa-elf ,-Werror |
21a6f6bb | 296 | |
8dacb7ef | 297 | powerpc --target=powerpc-eabi ,-Werror |
9b82661c | 298 | |
9f9d12b3 | 299 | s390 --target=s390-linux-gnu ,-Werror |
5769d3cd | 300 | |
5dbc6baa | 301 | sh --target=sh-elf ,-Werror |
079c8cd0 | 302 | --target=sh64-elf ,-Werror |
9b82661c | 303 | |
043c9cdc | 304 | sparc --target=sparc-elf ,-Werror |
9b82661c | 305 | |
181124bc | 306 | v850 --target=v850-elf ,-Werror |
21a6f6bb | 307 | |
043c9cdc | 308 | vax --target=vax-netbsd ,-Werror |
21a6f6bb | 309 | |
53fe9346 | 310 | x86-64 --target=x86_64-linux-gnu ,-Werror |
e4621584 | 311 | |
b6fcb393 | 312 | xstormy16 --target=xstormy16-elf |
7c0a2a0a CV |
313 | Corinna Vinschen vinschen@redhat.com |
314 | ||
fcc87af1 AC |
315 | All developers recognized by this file can make arbitrary changes to |
316 | OBSOLETE targets. | |
9b82661c | 317 | |
684e56bf AC |
318 | The Bourne shell script gdb_mbuild.sh can be used to rebuild all the |
319 | above targets. | |
5185fdd7 AC |
320 | |
321 | ||
8860ff2e AC |
322 | Host/Native: |
323 | ||
9b82661c AC |
324 | The Native maintainer is responsible for target specific native |
325 | support - typically shared libraries and quirks to procfs/ptrace/... | |
326 | The Native maintainer works with the Arch and Core maintainers when | |
327 | resolving more generic problems. | |
8860ff2e | 328 | |
9175c9a3 MC |
329 | The host maintainer ensures that gdb can be built as a cross debugger on |
330 | their platform. | |
5185fdd7 | 331 | |
f4d408c6 | 332 | AIX Joel Brobecker brobecker@adacore.com |
e306c308 | 333 | |
56a5d675 | 334 | djgpp native Eli Zaretskii eliz@gnu.org |
842330b4 | 335 | MS Windows (NT, '00, 9x, Me, XP) host & native |
859a326d | 336 | Chris Faylor cgf@alum.bu.edu |
ef7b4488 | 337 | GNU/Linux/x86 native & host |
ef7b4488 | 338 | Mark Kettenis kettenis@gnu.org |
6c8e04b5 DJ |
339 | GNU/Linux MIPS native & host |
340 | Daniel Jacobowitz dan@debian.org | |
26806ce2 | 341 | GNU/Linux m68k Andreas Schwab schwab@suse.de |
e255d535 | 342 | FreeBSD native & host Mark Kettenis kettenis@gnu.org |
5185fdd7 | 343 | |
9b82661c AC |
344 | |
345 | ||
5185fdd7 AC |
346 | Core: Generic components used by all of GDB |
347 | ||
f9e2d830 AC |
348 | tracing Michael Snyder msnyder@redhat.com |
349 | threads Michael Snyder msnyder@redhat.com | |
a8596edf | 350 | Mark Kettenis kettenis@gnu.org |
f4d408c6 | 351 | language support |
8de3c354 | 352 | C++ Daniel Jacobowitz dan@debian.org |
3771659b | 353 | Objective C support Adam Fedor fedor@gnu.org |
f4d408c6 | 354 | shared libs Kevin Buettner kevinb@redhat.com |
e306c308 | 355 | |
e8be95ae | 356 | documentation Eli Zaretskii eliz@gnu.org |
49101e1c | 357 | (including NEWS) |
f4d408c6 | 358 | testsuite |
5a703563 | 359 | gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com |
5a703563 FN |
360 | threads (gdb.threads) Michael Snyder msnyder@redhat.com |
361 | trace (gdb.trace) Michael Snyder msnyder@redhat.com | |
5185fdd7 AC |
362 | |
363 | ||
364 | UI: External (user) interfaces. | |
365 | ||
f4d408c6 | 366 | gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com |
54403c59 | 367 | Keith Seitz keiths@redhat.com |
f4d408c6 | 368 | libgui (w/foundry, sn) Keith Seitz keiths@redhat.com |
f5bca8e7 AC |
369 | |
370 | ||
371 | Misc: | |
372 | ||
3f289e6f AC |
373 | gdb/gdbserver Daniel Jacobowitz dan@debian.org |
374 | ||
f5bca8e7 | 375 | Makefile.in, configure* ALL |
7158fd7f AC |
376 | |
377 | mmalloc/ ALL Host maintainers | |
378 | ||
f779ca99 | 379 | sim/ See sim/MAINTAINERS |
5185fdd7 | 380 | |
9ec7faef | 381 | readline/ Master version: ftp://ftp.cwru.edu/pub/bash/ |
f4d408c6 | 382 | ALL |
9ec7faef AC |
383 | Host maintainers (host dependant parts) |
384 | (but get your changes into the master version) | |
385 | ||
f4d408c6 | 386 | tcl/ tk/ itcl/ ALL |
ef7b4488 | 387 | |
b2a74f99 DJ |
388 | |
389 | Authorized Committers | |
390 | --------------------- | |
391 | ||
392 | These are developers working on particular areas of GDB, who are trusted to | |
393 | commit their own (or other developers') patches in those areas without | |
394 | further review from a Global Maintainer or Responsible Maintainer. They are | |
395 | under no obligation to review posted patches - but, of course, are invited | |
396 | to do so! | |
397 | ||
f4d408c6 DJ |
398 | PowerPC Andrew Cagney cagney@gnu.org |
399 | CRIS Hans-Peter Nilsson hp@bitrange.com | |
400 | IA64 Jeff Johnston jjohnstn@redhat.com | |
401 | MIPS Joel Brobecker brobecker@adacore.com | |
402 | m32r Kei Sakamoto sakamoto.kei@renesas.com | |
403 | PowerPC Kevin Buettner kevinb@redhat.com | |
404 | CRIS Orjan Friberg orjanf@axis.com | |
405 | HPPA Randolph Chung tausq@debian.org | |
406 | S390 Ulrich Weigand uweigand@de.ibm.com | |
407 | djgpp DJ Delorie dj@delorie.com | |
408 | [Please use this address to contact DJ about DJGPP] | |
409 | tui Stephane Carrez stcarrez@nerim.fr | |
410 | ia64 Kevin Buettner kevinb@redhat.com | |
411 | AIX Kevin Buettner kevinb@redhat.com | |
412 | GNU/Linux PPC native Kevin Buettner kevinb@redhat.com | |
413 | gdb.java tests Anthony Green green@redhat.com | |
414 | FreeBSD native & host David O'Brien obrien@freebsd.org | |
415 | event loop Elena Zannoni ezannoni@redhat.com | |
416 | generic symtabs Elena Zannoni ezannoni@redhat.com | |
417 | dwarf readers Elena Zannoni ezannoni@redhat.com | |
418 | elf reader Elena Zannoni ezannoni@redhat.com | |
419 | stabs reader Elena Zannoni ezannoni@redhat.com | |
420 | readline/ Elena Zannoni ezannoni@redhat.com | |
421 | Kernel Object Display Fernando Nasser fnasser@redhat.com | |
422 | NetBSD native & host Jason Thorpe thorpej@netbsd.org | |
423 | Pascal support Pierre Muller muller@sources.redhat.com | |
424 | avr Theodore A. Roth troth@openavr.org | |
b2a74f99 DJ |
425 | |
426 | ||
e7745bde AC |
427 | Write After Approval |
428 | (alphabetic) | |
5185fdd7 | 429 | |
b76a2a57 AC |
430 | To get recommended for the Write After Approval list you need a valid |
431 | FSF assignment and have submitted one good patch. | |
432 | ||
b302179c | 433 | David Anderson davea@sgi.com |
871cce51 | 434 | John David Anglin dave.anglin@nrc-cnrc.gc.ca |
062103ba | 435 | Shrinivas Atre shrinivasa@kpitcummins.com |
627054c8 | 436 | Scott Bambrough scottb@netwinder.org |
ae2a31bf | 437 | Jan Beulich jbeulich@novell.com |
2f83030f | 438 | Jim Blandy jimb@codesourcery.com |
e7745bde | 439 | Philip Blundell philb@gnu.org |
627054c8 | 440 | Per Bothner per@bothner.com |
1581f359 | 441 | Joel Brobecker brobecker@adacore.com |
cdd463f9 | 442 | Dave Brolley brolley@redhat.com |
dbf5be1c | 443 | Paul Brook paul@codesourcery.com |
627054c8 | 444 | Kevin Buettner kevinb@redhat.com |
1db2a798 | 445 | Andrew Cagney cagney@gnu.org |
58e23df4 | 446 | David Carlton carlton@bactrian.org |
627054c8 | 447 | Stephane Carrez stcarrez@nerim.fr |
68e39e73 | 448 | Michael Chastain mec.gnu@mindspring.com |
e04e8f8a | 449 | Eric Christopher echristo@apple.com |
700c15aa | 450 | Randolph Chung tausq@debian.org |
f9e2d830 | 451 | Nick Clifton nickc@redhat.com |
f4d408c6 | 452 | J.T. Conklin jtc@acorntoolworks.com |
56296155 | 453 | Brendan Conoboy blc@redhat.com |
eb944380 | 454 | DJ Delorie dj@redhat.com |
eb944380 | 455 | Philippe De Muyter phdm@macqel.be |
8bfdb672 | 456 | Dhananjay Deshpande dhananjayd@kpitcummins.com |
6a41ff59 | 457 | Klee Dienes kdienes@apple.com |
dd96c05b | 458 | Richard Earnshaw rearnsha@arm.com |
3ad97651 | 459 | Steve Ellcey sje@cup.hp.com |
627054c8 | 460 | Frank Ch. Eigler fche@redhat.com |
523f6a27 | 461 | Ben Elliston bje@gnu.org |
e92f3704 JG |
462 | Adam Fedor fedor@gnu.org |
463 | Fred Fish fnf@ninemoons.com | |
283f90a7 | 464 | Brian Ford ford@vss.fsi.com |
e92f3704 | 465 | Orjan Friberg orjanf@axis.com |
386d4518 | 466 | Paul Gilliam pgilliam@us.ibm.com |
cb123844 | 467 | Raoul Gough RaoulGough@yahoo.co.uk |
627054c8 | 468 | Anthony Green green@redhat.com |
181c3369 | 469 | Matthew Green mrg@eterna.com.au |
a4ab2b5d | 470 | Jerome Guitton guitton@act-europe.fr |
1005d5ef | 471 | Ben Harris bjh21@netbsd.org |
23b95bcb | 472 | Richard Henderson rth@redhat.com |
814b3ba0 | 473 | Aldy Hernandez aldyh@redhat.com |
e7745bde AC |
474 | Paul Hilfinger hilfinger@gnat.com |
475 | Matt Hiller hiller@redhat.com | |
ed42d87b | 476 | Kazu Hirata kazu@cs.umass.edu |
e7745bde AC |
477 | Jeff Holcomb jeffh@redhat.com |
478 | Don Howard dhoward@redhat.com | |
479 | Martin Hunt hunt@redhat.com | |
6a41ff59 | 480 | Jim Ingham jingham@apple.com |
a80493b8 | 481 | Baurzhan Ismagulov ibr@radix50.net |
7d97d5e2 | 482 | Manoj Iyer manjo@austin.ibm.com |
2740bf6c | 483 | Daniel Jacobowitz dan@debian.org |
37965979 | 484 | Andreas Jaeger aj@suse.de |
7e3cec17 | 485 | Jeff Johnston jjohnstn@redhat.com |
e7745bde | 486 | Geoff Keating geoffk@redhat.com |
627054c8 | 487 | Mark Kettenis kettenis@gnu.org |
f4d408c6 | 488 | Jim Kingdon kingdon@panix.com |
f09cffe3 | 489 | Jonathan Larmour jlarmour@redhat.co.uk |
eb944380 | 490 | Jeff Law law@redhat.com |
b1bd302e | 491 | David Lecomber david@streamline-computing.com |
627054c8 | 492 | Robert Lipe rjl@sco.com |
e7745bde | 493 | H.J. Lu hjl@lucon.org |
627054c8 | 494 | Michal Ludvig mludvig@suse.cz |
f9e2d830 | 495 | Glen McCready gkm@redhat.com |
ac2e0304 | 496 | Greg McGary greg@mcgary.org |
a8cbc6f7 | 497 | Roland McGrath roland@redhat.com |
723e0e3d | 498 | Bryce McKinlay mckinlay@redhat.com |
39c22d1a | 499 | Jason Merrill jason@redhat.com |
627054c8 | 500 | David S. Miller davem@redhat.com |
89a72f9c | 501 | Mark Mitchell mark@codesourcery.com |
da615bee | 502 | Marko Mlinar markom@opencores.org |
ecd1107e | 503 | Alan Modra amodra@bigpond.net.au |
6d6b80e5 | 504 | Jason Molenda jmolenda@apple.com |
47b95330 | 505 | Pierre Muller muller@sources.redhat.com |
3d38a0a5 | 506 | Joseph Myers joseph@codesourcery.com |
627054c8 | 507 | Fernando Nasser fnasser@redhat.com |
d0f853e1 | 508 | Nathanael Nerode neroden@gcc.gnu.org |
6eecb1c8 | 509 | Hans-Peter Nilsson hp@bitrange.com |
627054c8 | 510 | David O'Brien obrien@freebsd.org |
2748f097 | 511 | Alexandre Oliva aoliva@redhat.com |
33e6b12b | 512 | Ramana Radhakrishnan ramana.radhakrishnan@codito.com |
58ad5041 | 513 | Frederic Riss frederic.riss@st.com |
dfea300e | 514 | Tom Rix trix@redhat.com |
e1124681 | 515 | Nick Roberts nickrob@snap.net.nz |
a8cbc6f7 | 516 | Bob Rossi bob_rossi@cox.net |
de18ac1f | 517 | Theodore A. Roth troth@openavr.org |
627054c8 | 518 | Ian Roxborough irox@redhat.com |
83b4a0fe | 519 | Grace Sainsbury graces@redhat.com |
29ceeffb | 520 | Kei Sakamoto sakamoto.kei@renesas.com |
39f0ec5c | 521 | Mark Salter msalter@redhat.com |
d738fe6d | 522 | Richard Sandiford richard@codesourcery.com |
f4d408c6 | 523 | Peter Schauer Peter.Schauer@mytum.de |
49d5aff7 | 524 | Andreas Schwab schwab@suse.de |
f9e2d830 | 525 | Keith Seitz keiths@redhat.com |
eb944380 | 526 | Stan Shebs shebs@apple.com |
36479eb1 | 527 | Aidan Skinner aidan@velvet.net |
5f3b5248 | 528 | Jiri Smid smid@suse.cz |
e7745bde | 529 | David Smith dsmith@redhat.com |
de3a8c23 | 530 | Stephen P. Smith ischis2@cox.net |
02da6206 | 531 | Jackie Smith Cashion jsmith@redhat.com |
627054c8 | 532 | Michael Snyder msnyder@redhat.com |
41ae02c9 | 533 | Petr Sorfa petrs@caldera.com |
bd73ccbd | 534 | Andrew Stubbs andrew.stubbs@st.com |
3517749c | 535 | Ian Lance Taylor ian@airs.com |
e7745bde | 536 | Gary Thomas gthomas@redhat.com |
12b21d12 | 537 | Jason Thorpe thorpej@netbsd.org |
f9e2d830 | 538 | Tom Tromey tromey@redhat.com |
f56c189d | 539 | David Ung davidu@mips.com |
0c67cbe9 | 540 | D Venkatasubramanian dvenkat@noida.hcltech.com |
7717fda3 | 541 | Corinna Vinschen vinschen@redhat.com |
aedf1c5b | 542 | Keith Walker keith.walker@arm.com |
9a3c34fe | 543 | Kris Warkentin kewarken@qnx.com |
090ddb2a | 544 | Ulrich Weigand uweigand@de.ibm.com |
0b71f08f | 545 | Nathan Williams nathanw@wasabisystems.com |
fcd182f9 | 546 | Jim Wilson wilson@specifixinc.com |
627054c8 AC |
547 | Elena Zannoni ezannoni@redhat.com |
548 | Eli Zaretskii eliz@gnu.org | |
72429025 | 549 | Wu Zhou woodzltc@cn.ibm.com |
ba0e80db | 550 | Yoshinori Sato ysato@users.sourceforge.jp |
e7745bde | 551 | |
15929d05 | 552 | |
3a0c66d4 AC |
553 | Past Maintainers |
554 | ||
f4d408c6 DJ |
555 | Whenever removing yourself, or someone else, from this file, consider |
556 | listing their areas of development here for posterity. | |
557 | ||
47b95330 AC |
558 | Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com |
559 | Jeff Law (hppa) law at cygnus dot com | |
560 | Daniel Berlin (C++ support) dan at cgsoftware dot com | |
7fe4d0d2 AC |
561 | Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com |
562 | David Taylor (d10v, sparc, utils, defs, | |
563 | expression evaluator, language support) taylor at candd dot org | |
f4d408c6 | 564 | J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com |
f779ca99 | 565 | Frank Ch. Eigler (sim) fche at redhat dot com |
8a81a99e | 566 | Per Bothner (Java) per at bothner dot com |
23b7d5f3 | 567 | Anthony Green (Java) green at redhat dot com |
69aec09b | 568 | Fernando Nasser (testsuite/, mi, cli) fnasser at redhat dot com |
5aae53e5 | 569 | Mark Salter (testsuite/lib+config) msalter at redhat dot com |
f4d408c6 DJ |
570 | Jim Kingdon (web pages) kingdon at panix dot com |
571 | Jim Ingham (gdbtk, libgui) jingham at apple dot com | |
572 | Mark Kettenis (hurd native) kettenis at gnu dot org | |
573 | Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com | |
574 | Robert Lipe (SCO/Unixware) rjl at sco dot com | |
575 | Peter Schauer (global, AIX, xcoffsolib, | |
576 | Solaris/x86) Peter.Schauer at mytum dot de | |
577 | Scott Bambrough (ARM) scottb at netwinder dot org | |
578 | Philippe De Muyter (coff) phdm at macqel dot be | |
579 | Michael Chastain (testsuite) mec.gnu at mindspring dot com | |
5ecaa7dd | 580 | |
3a0c66d4 AC |
581 | |
582 | ||
e33e9692 | 583 | Folks that have been caught up in a paper trail: |
dfe25b3a | 584 | |
58e23df4 | 585 | David Carlton carlton@bactrian.org |