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 | ||
81e0e940 EZ |
98 | For documentation changes, about the only kind of fix that is obvious |
99 | is correction of a typo or bad English usage. | |
100 | ||
e990a46e AC |
101 | |
102 | GDB Steering Committee | |
b2a74f99 | 103 | ---------------------- |
e990a46e AC |
104 | |
105 | The members of the GDB Steering Committee are the FSF-appointed | |
106 | maintainers of the GDB project. | |
107 | ||
b2a74f99 DJ |
108 | The Steering Committee has final authority for all GDB-related topics; |
109 | they may make whatever changes that they deem necessary, or that the FSF | |
110 | requests. However, they are generally not involved in day-to-day | |
111 | development. | |
112 | ||
113 | The current members of the steering committee are listed below, in | |
114 | alphabetical order. Their affiliations are provided for reference only - | |
115 | their membership on the Steering Committee is individual and not through | |
116 | their affiliation, and they act on behalf of the GNU project. | |
117 | ||
5eeba8d4 | 118 | Jim Blandy (Mozilla) |
e990a46e AC |
119 | Andrew Cagney (Red Hat) |
120 | Robert Dewar (AdaCore, NYU) | |
121 | Klee Dienes (Apple) | |
122 | Paul Hilfinger (UC Berkeley) | |
123 | Dan Jacobowitz (CodeSourcery) | |
336de56d | 124 | Stan Shebs (CodeSourcery) |
e990a46e AC |
125 | Richard Stallman (FSF) |
126 | Ian Lance Taylor (C2) | |
127 | Todd Whitesel | |
ef7b4488 | 128 | |
5185fdd7 | 129 | |
b2a74f99 DJ |
130 | Global Maintainers |
131 | ------------------ | |
132 | ||
133 | The global maintainers may review and commit any change to GDB, except in | |
134 | areas with a Responsible Maintainer available. For major changes, or | |
135 | changes to areas with other active developers, global maintainers are | |
136 | strongly encouraged to post their own patches for feedback before | |
137 | committing. | |
138 | ||
139 | The global maintainers are responsible for reviewing patches to any area | |
140 | for which no Responsible Maintainer is listed. | |
141 | ||
142 | Global maintainers also have the authority to revert patches which should | |
143 | not have been applied, e.g. patches which were not approved, controversial | |
144 | patches committed under the Obvious Fix Rule, patches with important bugs | |
145 | that can't be immediately fixed, or patches which go against an accepted and | |
146 | documented roadmap for GDB development. Any global maintainer may request | |
147 | the reversion of a patch. If no global maintainer, or responsible | |
148 | maintainer in the affected areas, supports the patch (except for the | |
149 | maintainer who originally committed it), then after 48 hours the maintainer | |
150 | who called for the reversion may revert the patch. | |
151 | ||
152 | No one may reapply a reverted patch without the agreement of the maintainer | |
153 | who reverted it, or bringing the issue to the GDB Steering Committee for | |
154 | discussion. | |
155 | ||
156 | At the moment there are no documented roadmaps for GDB development; in the | |
157 | future, if there are, a reference to the list will be included here. | |
158 | ||
159 | The current global maintainers are (in alphabetical order): | |
5185fdd7 | 160 | |
3cd9d164 | 161 | Pedro Alves pedro@codesourcery.com |
a367a1f2 | 162 | Jim Blandy jimb@red-bean.com |
e933291e | 163 | Joel Brobecker brobecker@adacore.com |
904507ce | 164 | Kevin Buettner kevinb@redhat.com |
1db2a798 | 165 | Andrew Cagney cagney@gnu.org |
bf0d7e9c | 166 | Doug Evans dje@google.com |
322be962 | 167 | Daniel Jacobowitz dan@codesourcery.com |
1b57acd2 | 168 | Mark Kettenis kettenis@gnu.org |
336de56d | 169 | Stan Shebs stan@codesourcery.com |
11fa8e43 | 170 | Michael Snyder msnyder@vmware.com |
d7dc3873 | 171 | Tom Tromey tromey@redhat.com |
03f597d5 | 172 | Ulrich Weigand Ulrich.Weigand@de.ibm.com |
692263b8 | 173 | Elena Zannoni elena.zannoni@oracle.com |
904507ce | 174 | Eli Zaretskii eliz@gnu.org |
0e780a22 | 175 | Jan Kratochvil jkratoch@redhat.com |
5185fdd7 | 176 | |
f5bca8e7 | 177 | |
b2a74f99 DJ |
178 | Release Manager |
179 | --------------- | |
5185fdd7 | 180 | |
b2a74f99 | 181 | The current release manager is: Joel Brobecker <brobecker@adacore.com> |
5185fdd7 | 182 | |
b2a74f99 | 183 | His responsibilities are: |
36c2118f | 184 | |
b2a74f99 | 185 | * organizing, scheduling, and managing releases of GDB. |
538aae9d | 186 | |
b2a74f99 DJ |
187 | * deciding the approval and commit policies for release branches, |
188 | and can change them as needed. | |
5185fdd7 | 189 | |
58cfabe6 | 190 | |
58cfabe6 | 191 | |
b2a74f99 DJ |
192 | Patch Champions |
193 | --------------- | |
58cfabe6 | 194 | |
b2a74f99 DJ |
195 | These volunteers track all patches submitted to the gdb-patches list. They |
196 | endeavor to prevent any posted patch from being overlooked; work with | |
197 | contributors to meet GDB's coding style and general requirements, along with | |
198 | FSF copyright assignments; remind (ping) responsible maintainers to review | |
199 | patches; and ensure that contributors are given credit. | |
58cfabe6 | 200 | |
b2a74f99 | 201 | Current patch champions (in alphabetical order): |
54c92070 | 202 | |
c9f7217e | 203 | Randolph Chung <tausq@debian.org> |
58cfabe6 | 204 | |
a60a53c5 | 205 | |
a60a53c5 | 206 | |
b2a74f99 DJ |
207 | Responsible Maintainers |
208 | ----------------------- | |
209 | ||
210 | These developers have agreed to review patches in specific areas of GDB, in | |
211 | which they have knowledge and experience. These areas are generally broad; | |
212 | the role of a responsible maintainer is to provide coherent and cohesive | |
213 | structure within their area of GDB, to assure that patches from many | |
214 | different contributors all work together for the best results. | |
a60a53c5 | 215 | |
b2a74f99 DJ |
216 | Global maintainers will defer to responsible maintainers within their areas, |
217 | as long as the responsible maintainer is active. Active means that | |
218 | responsible maintainers agree to review submitted patches in their area | |
219 | promptly; patches and followups should generally be answered within a week. | |
220 | If a responsible maintainer is interested in reviewing a patch but will not | |
221 | have time within a week of posting, the maintainer should send an | |
222 | acknowledgement of the patch to the gdb-patches mailing list, and | |
223 | plan to follow up with a review within a month. These deadlines are for | |
224 | initial responses to a patch - if the maintainer has suggestions | |
225 | or questions, it may take an extended discussion before the patch | |
226 | is ready to commit. There are no written requirements for discussion, | |
227 | but maintainers are asked to be responsive. | |
228 | ||
229 | If a responsible maintainer misses these deadlines occasionally (e.g. | |
230 | vacation or unexpected workload), it's not a disaster - any global | |
231 | maintainer may step in to review the patch. But sometimes life intervenes | |
232 | more permanently, and a maintainer may no longer have time for these duties. | |
233 | When this happens, he or she should step down (either into the Authorized | |
234 | Committers section if still interested in the area, or simply removed from | |
235 | the list of Responsible Maintainers if not). | |
236 | ||
237 | If a responsible maintainer is unresponsive for an extended period of time | |
238 | without stepping down, please contact the Global Maintainers; they will try | |
239 | to contact the maintainer directly and fix the problem - potentially by | |
240 | removing that maintainer from their listed position. | |
241 | ||
242 | If there are several maintainers for a given domain then any one of them | |
243 | may review a submitted patch. | |
a60a53c5 | 244 | |
c1bab85b | 245 | Target Instruction Set Architectures: |
8860ff2e | 246 | |
91a533d4 AC |
247 | The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI |
248 | (Operating System / Application Binary Interface) issues including CPU | |
249 | variants. | |
250 | ||
251 | The Target/Architecture maintainer works with the host maintainer when | |
252 | resolving build issues. The Target/Architecture maintainer works with | |
253 | the native maintainer when resolving ABI issues. | |
5185fdd7 | 254 | |
8f9cbe01 | 255 | alpha --target=alpha-elf ,-Werror |
21a6f6bb | 256 | |
66140c26 | 257 | arm --target=arm-elf ,-Werror |
26806ce2 | 258 | Richard Earnshaw rearnsha@arm.com |
9b82661c | 259 | |
e33ce519 | 260 | avr --target=avr ,-Werror |
b06adb81 | 261 | Tristan Gingold gingold@adacore.com |
e33ce519 | 262 | |
cb5c8c39 DJ |
263 | cris --target=cris-elf ,-Werror , |
264 | (sim does not build with -Werror) | |
93755ae6 | 265 | |
53e8aaea | 266 | frv --target=frv-elf ,-Werror |
53e8aaea | 267 | |
87d088f5 | 268 | h8300 --target=h8300-elf ,-Werror |
9b82661c | 269 | |
c1bab85b | 270 | i386 --target=i386-elf ,-Werror |
21a6f6bb AC |
271 | Mark Kettenis kettenis@gnu.org |
272 | ||
32089c7c AC |
273 | ia64 --target=ia64-linux-gnu ,-Werror |
274 | (--target=ia64-elf broken) | |
606139a1 | 275 | Jan Kratochvil jan.kratochvil@redhat.com |
9b82661c | 276 | |
c28c63d8 JB |
277 | lm32 --target=lm32-elf ,-Werror |
278 | ||
96309189 | 279 | m32c --target=m32c-elf ,-Werror |
96309189 | 280 | |
9644bbdd | 281 | m32r --target=m32r-elf ,-Werror |
9b82661c | 282 | |
53fe9346 | 283 | m68hc11 --target=m68hc11-elf ,-Werror , |
2be99286 | 284 | Stephane Carrez stcarrez@nerim.fr |
9b82661c | 285 | |
043c9cdc | 286 | m68k --target=m68k-elf ,-Werror |
9b82661c | 287 | |
1698f4e7 MK |
288 | m88k --target=m88k-openbsd ,-Werror |
289 | Mark Kettenis kettenis@gnu.org | |
9b82661c | 290 | |
9445aa30 | 291 | mcore Deleted |
9b82661c | 292 | |
01c996c1 KB |
293 | mep --target=mep-elf ,-Werror |
294 | Kevin Buettner kevinb@redhat.com | |
295 | ||
599ec134 JB |
296 | microblaze --target=microblaze-xilinx-elf ,-Werror |
297 | --target=microblaze-linux-gnu ,-Werror | |
298 | Michael Eager eager@eagercon.com | |
299 | ||
c1bab85b | 300 | mips --target=mips-elf ,-Werror |
9b82661c | 301 | |
87d088f5 AC |
302 | mn10300 --target=mn10300-elf broken |
303 | (sim/ dies with make -j) | |
11fa8e43 | 304 | Michael Snyder msnyder@vmware.com |
9b82661c | 305 | |
d7066cce AG |
306 | moxie --target=moxie-elf ,-Werror |
307 | Anthony Green green@moxielogic.com | |
308 | ||
37ebea84 KB |
309 | ms1 --target=ms1-elf ,-Werror |
310 | Kevin Buettner kevinb@redhat.com | |
311 | ||
9445aa30 | 312 | ns32k Deleted |
9b82661c | 313 | |
93449403 | 314 | pa --target=hppa-elf ,-Werror |
21a6f6bb | 315 | |
8dacb7ef | 316 | powerpc --target=powerpc-eabi ,-Werror |
9b82661c | 317 | |
9f9d12b3 | 318 | s390 --target=s390-linux-gnu ,-Werror |
5769d3cd | 319 | |
27fd2f50 Q |
320 | score --target=score-elf |
321 | Qinwei qinwei@sunnorth.com.cn | |
322 | ||
5dbc6baa | 323 | sh --target=sh-elf ,-Werror |
079c8cd0 | 324 | --target=sh64-elf ,-Werror |
9b82661c | 325 | |
cb5c8c39 DJ |
326 | sparc --target=sparc64-solaris2.10 ,-Werror |
327 | (--target=sparc-elf broken) | |
9b82661c | 328 | |
d1320b0b UW |
329 | spu --target=spu-elf ,-Werror |
330 | Ulrich Weigand uweigand@de.ibm.com | |
331 | ||
181124bc | 332 | v850 --target=v850-elf ,-Werror |
21a6f6bb | 333 | |
043c9cdc | 334 | vax --target=vax-netbsd ,-Werror |
21a6f6bb | 335 | |
53fe9346 | 336 | x86-64 --target=x86_64-linux-gnu ,-Werror |
e4621584 | 337 | |
b6fcb393 | 338 | xstormy16 --target=xstormy16-elf |
7c0a2a0a CV |
339 | Corinna Vinschen vinschen@redhat.com |
340 | ||
9cd84602 MG |
341 | xtensa --target=xtensa-elf |
342 | Maxim Grigoriev maxim2405@gmail.com | |
343 | ||
fcc87af1 AC |
344 | All developers recognized by this file can make arbitrary changes to |
345 | OBSOLETE targets. | |
9b82661c | 346 | |
684e56bf AC |
347 | The Bourne shell script gdb_mbuild.sh can be used to rebuild all the |
348 | above targets. | |
5185fdd7 AC |
349 | |
350 | ||
8860ff2e AC |
351 | Host/Native: |
352 | ||
9b82661c AC |
353 | The Native maintainer is responsible for target specific native |
354 | support - typically shared libraries and quirks to procfs/ptrace/... | |
355 | The Native maintainer works with the Arch and Core maintainers when | |
356 | resolving more generic problems. | |
8860ff2e | 357 | |
9175c9a3 MC |
358 | The host maintainer ensures that gdb can be built as a cross debugger on |
359 | their platform. | |
5185fdd7 | 360 | |
f4d408c6 | 361 | AIX Joel Brobecker brobecker@adacore.com |
3e6b0399 | 362 | Darwin Tristan Gingold gingold@adacore.com |
56a5d675 | 363 | djgpp native Eli Zaretskii eliz@gnu.org |
e0f2823e | 364 | GNU Hurd Alfred M. Szmidt ams@gnu.org |
842330b4 | 365 | MS Windows (NT, '00, 9x, Me, XP) host & native |
859a326d | 366 | Chris Faylor cgf@alum.bu.edu |
ef7b4488 | 367 | GNU/Linux/x86 native & host |
ef7b4488 | 368 | Mark Kettenis kettenis@gnu.org |
6c8e04b5 | 369 | GNU/Linux MIPS native & host |
322be962 | 370 | Daniel Jacobowitz dan@codesourcery.com |
a2f63f5e | 371 | GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org |
e255d535 | 372 | FreeBSD native & host Mark Kettenis kettenis@gnu.org |
5185fdd7 | 373 | |
9b82661c AC |
374 | |
375 | ||
5185fdd7 AC |
376 | Core: Generic components used by all of GDB |
377 | ||
11fa8e43 MS |
378 | tracing Michael Snyder msnyder@vmware.com |
379 | threads Michael Snyder msnyder@vmware.com | |
a8596edf | 380 | Mark Kettenis kettenis@gnu.org |
f4d408c6 | 381 | language support |
b33682a7 DJ |
382 | Ada Joel Brobecker brobecker@adacore.com |
383 | Paul Hilfinger hilfinger@gnat.com | |
322be962 | 384 | C++ Daniel Jacobowitz dan@codesourcery.com |
3771659b | 385 | Objective C support Adam Fedor fedor@gnu.org |
f4d408c6 | 386 | shared libs Kevin Buettner kevinb@redhat.com |
d9bf65d5 | 387 | MI interface Vladimir Prus vladimir@codesourcery.com |
e306c308 | 388 | |
e8be95ae | 389 | documentation Eli Zaretskii eliz@gnu.org |
49101e1c | 390 | (including NEWS) |
f4d408c6 | 391 | testsuite |
5a703563 | 392 | gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com |
11fa8e43 MS |
393 | threads (gdb.threads) Michael Snyder msnyder@vmware.com |
394 | trace (gdb.trace) Michael Snyder msnyder@vmware.com | |
5185fdd7 AC |
395 | |
396 | ||
397 | UI: External (user) interfaces. | |
398 | ||
f4d408c6 | 399 | gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com |
54403c59 | 400 | Keith Seitz keiths@redhat.com |
f4d408c6 | 401 | libgui (w/foundry, sn) Keith Seitz keiths@redhat.com |
f5bca8e7 AC |
402 | |
403 | ||
404 | Misc: | |
405 | ||
322be962 | 406 | gdb/gdbserver Daniel Jacobowitz dan@codesourcery.com |
3f289e6f | 407 | |
f5bca8e7 | 408 | Makefile.in, configure* ALL |
7158fd7f AC |
409 | |
410 | mmalloc/ ALL Host maintainers | |
411 | ||
f779ca99 | 412 | sim/ See sim/MAINTAINERS |
5185fdd7 | 413 | |
9ec7faef | 414 | readline/ Master version: ftp://ftp.cwru.edu/pub/bash/ |
f4d408c6 | 415 | ALL |
9ec7faef AC |
416 | Host maintainers (host dependant parts) |
417 | (but get your changes into the master version) | |
418 | ||
f4d408c6 | 419 | tcl/ tk/ itcl/ ALL |
ef7b4488 | 420 | |
b2a74f99 DJ |
421 | |
422 | Authorized Committers | |
423 | --------------------- | |
424 | ||
425 | These are developers working on particular areas of GDB, who are trusted to | |
426 | commit their own (or other developers') patches in those areas without | |
427 | further review from a Global Maintainer or Responsible Maintainer. They are | |
428 | under no obligation to review posted patches - but, of course, are invited | |
429 | to do so! | |
430 | ||
f4d408c6 | 431 | PowerPC Andrew Cagney cagney@gnu.org |
cfefc99a | 432 | CRIS Hans-Peter Nilsson hp@axis.com |
f4d408c6 DJ |
433 | IA64 Jeff Johnston jjohnstn@redhat.com |
434 | MIPS Joel Brobecker brobecker@adacore.com | |
435 | m32r Kei Sakamoto sakamoto.kei@renesas.com | |
436 | PowerPC Kevin Buettner kevinb@redhat.com | |
437 | CRIS Orjan Friberg orjanf@axis.com | |
438 | HPPA Randolph Chung tausq@debian.org | |
439 | S390 Ulrich Weigand uweigand@de.ibm.com | |
440 | djgpp DJ Delorie dj@delorie.com | |
441 | [Please use this address to contact DJ about DJGPP] | |
442 | tui Stephane Carrez stcarrez@nerim.fr | |
443 | ia64 Kevin Buettner kevinb@redhat.com | |
444 | AIX Kevin Buettner kevinb@redhat.com | |
445 | GNU/Linux PPC native Kevin Buettner kevinb@redhat.com | |
446 | gdb.java tests Anthony Green green@redhat.com | |
447 | FreeBSD native & host David O'Brien obrien@freebsd.org | |
692263b8 JB |
448 | event loop Elena Zannoni elena.zannoni@oracle.com |
449 | generic symtabs Elena Zannoni elena.zannoni@oracle.com | |
450 | dwarf readers Elena Zannoni elena.zannoni@oracle.com | |
451 | elf reader Elena Zannoni elena.zannoni@oracle.com | |
452 | stabs reader Elena Zannoni elena.zannoni@oracle.com | |
453 | readline/ Elena Zannoni elena.zannoni@oracle.com | |
f4d408c6 | 454 | NetBSD native & host Jason Thorpe thorpej@netbsd.org |
0643c12e | 455 | Pascal support Pierre Muller muller@sourceware.org |
f4d408c6 | 456 | avr Theodore A. Roth troth@openavr.org |
13942a42 | 457 | Modula-2 support Gaius Mulley gaius@glam.ac.uk |
b2a74f99 DJ |
458 | |
459 | ||
e7745bde AC |
460 | Write After Approval |
461 | (alphabetic) | |
5185fdd7 | 462 | |
b76a2a57 AC |
463 | To get recommended for the Write After Approval list you need a valid |
464 | FSF assignment and have submitted one good patch. | |
465 | ||
20dad8ea | 466 | Pedro Alves pedro_alves@portugalmail.pt |
b302179c | 467 | David Anderson davea@sgi.com |
871cce51 | 468 | John David Anglin dave.anglin@nrc-cnrc.gc.ca |
062103ba | 469 | Shrinivas Atre shrinivasa@kpitcummins.com |
627054c8 | 470 | Scott Bambrough scottb@netwinder.org |
07bed550 | 471 | Thiago Jung Bauermann bauerman@br.ibm.com |
7a893eb8 | 472 | Jon Beniston jon@beniston.com |
ae2a31bf | 473 | Jan Beulich jbeulich@novell.com |
2f83030f | 474 | Jim Blandy jimb@codesourcery.com |
e7745bde | 475 | Philip Blundell philb@gnu.org |
627054c8 | 476 | Per Bothner per@bothner.com |
1581f359 | 477 | Joel Brobecker brobecker@adacore.com |
cdd463f9 | 478 | Dave Brolley brolley@redhat.com |
dbf5be1c | 479 | Paul Brook paul@codesourcery.com |
5b031165 | 480 | Julian Brown julian@codesourcery.com |
627054c8 | 481 | Kevin Buettner kevinb@redhat.com |
1db2a798 | 482 | Andrew Cagney cagney@gnu.org |
58e23df4 | 483 | David Carlton carlton@bactrian.org |
627054c8 | 484 | Stephane Carrez stcarrez@nerim.fr |
68e39e73 | 485 | Michael Chastain mec.gnu@mindspring.com |
f32b2f09 | 486 | Renquan Cheng crq@gcc.gnu.org |
e04e8f8a | 487 | Eric Christopher echristo@apple.com |
700c15aa | 488 | Randolph Chung tausq@debian.org |
f9e2d830 | 489 | Nick Clifton nickc@redhat.com |
f4d408c6 | 490 | J.T. Conklin jtc@acorntoolworks.com |
56296155 | 491 | Brendan Conoboy blc@redhat.com |