*** empty log message ***
[deliverable/binutils-gdb.git] / gdb / MAINTAINERS
1 GDB Maintainers
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
98 For documentation changes, about the only kind of fix that is obvious
99 is correction of a typo or bad English usage.
100
101
102 GDB Steering Committee
103 ----------------------
104
105 The members of the GDB Steering Committee are the FSF-appointed
106 maintainers of the GDB project.
107
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
118 Jim Blandy (CodeSourcery)
119 Andrew Cagney (Red Hat)
120 Robert Dewar (AdaCore, NYU)
121 Klee Dienes (Apple)
122 Paul Hilfinger (UC Berkeley)
123 Dan Jacobowitz (CodeSourcery)
124 Stan Shebs (Mozilla)
125 Richard Stallman (FSF)
126 Ian Lance Taylor (C2)
127 Todd Whitesel
128
129
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):
160
161 Jim Blandy jimb@codesourcery.com
162 Joel Brobecker brobecker@adacore.com
163 Kevin Buettner kevinb@redhat.com
164 Andrew Cagney cagney@gnu.org
165 Fred Fish fnf@ninemoons.com
166 Daniel Jacobowitz dan@debian.org
167 Mark Kettenis kettenis@gnu.org
168 Stan Shebs shebs@mozilla.com
169 Michael Snyder Michael.Snyder@access-company.com
170 Ulrich Weigand Ulrich.Weigand@de.ibm.com
171 Elena Zannoni ezannoni@redhat.com
172 Eli Zaretskii eliz@gnu.org
173
174
175 Release Manager
176 ---------------
177
178 The current release manager is: Joel Brobecker <brobecker@adacore.com>
179
180 His responsibilities are:
181
182 * organizing, scheduling, and managing releases of GDB.
183
184 * deciding the approval and commit policies for release branches,
185 and can change them as needed.
186
187
188
189 Patch Champions
190 ---------------
191
192 These volunteers track all patches submitted to the gdb-patches list. They
193 endeavor to prevent any posted patch from being overlooked; work with
194 contributors to meet GDB's coding style and general requirements, along with
195 FSF copyright assignments; remind (ping) responsible maintainers to review
196 patches; and ensure that contributors are given credit.
197
198 Current patch champions (in alphabetical order):
199
200 Randolph Chung <tausq@debian.org>
201 Daniel Jacobowitz <dan@debian.org>
202
203
204
205 Responsible Maintainers
206 -----------------------
207
208 These developers have agreed to review patches in specific areas of GDB, in
209 which they have knowledge and experience. These areas are generally broad;
210 the role of a responsible maintainer is to provide coherent and cohesive
211 structure within their area of GDB, to assure that patches from many
212 different contributors all work together for the best results.
213
214 Global maintainers will defer to responsible maintainers within their areas,
215 as long as the responsible maintainer is active. Active means that
216 responsible maintainers agree to review submitted patches in their area
217 promptly; patches and followups should generally be answered within a week.
218 If a responsible maintainer is interested in reviewing a patch but will not
219 have time within a week of posting, the maintainer should send an
220 acknowledgement of the patch to the gdb-patches mailing list, and
221 plan to follow up with a review within a month. These deadlines are for
222 initial responses to a patch - if the maintainer has suggestions
223 or questions, it may take an extended discussion before the patch
224 is ready to commit. There are no written requirements for discussion,
225 but maintainers are asked to be responsive.
226
227 If a responsible maintainer misses these deadlines occasionally (e.g.
228 vacation or unexpected workload), it's not a disaster - any global
229 maintainer may step in to review the patch. But sometimes life intervenes
230 more permanently, and a maintainer may no longer have time for these duties.
231 When this happens, he or she should step down (either into the Authorized
232 Committers section if still interested in the area, or simply removed from
233 the list of Responsible Maintainers if not).
234
235 If a responsible maintainer is unresponsive for an extended period of time
236 without stepping down, please contact the Global Maintainers; they will try
237 to contact the maintainer directly and fix the problem - potentially by
238 removing that maintainer from their listed position.
239
240 If there are several maintainers for a given domain then any one of them
241 may review a submitted patch.
242
243 Target Instruction Set Architectures:
244
245 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
246 (Operating System / Application Binary Interface) issues including CPU
247 variants.
248
249 The Target/Architecture maintainer works with the host maintainer when
250 resolving build issues. The Target/Architecture maintainer works with
251 the native maintainer when resolving ABI issues.
252
253 alpha --target=alpha-elf ,-Werror
254
255 arm --target=arm-elf ,-Werror
256 Richard Earnshaw rearnsha@arm.com
257
258 avr --target=avr ,-Werror
259
260 cris --target=cris-elf ,-Werror ,
261 (sim does not build with -Werror)
262
263 frv --target=frv-elf ,-Werror
264
265 h8300 --target=h8300-elf ,-Werror
266
267 i386 --target=i386-elf ,-Werror
268 Mark Kettenis kettenis@gnu.org
269
270 ia64 --target=ia64-linux-gnu ,-Werror
271 (--target=ia64-elf broken)
272
273 m32c --target=m32c-elf ,-Werror
274 Jim Blandy, jimb@codesourcery.com
275
276 m32r --target=m32r-elf ,-Werror
277
278 m68hc11 --target=m68hc11-elf ,-Werror ,
279 Stephane Carrez stcarrez@nerim.fr
280
281 m68k --target=m68k-elf ,-Werror
282
283 m88k --target=m88k-openbsd ,-Werror
284 Mark Kettenis kettenis@gnu.org
285
286 mcore Deleted
287
288 mep --target=mep-elf ,-Werror
289 Kevin Buettner kevinb@redhat.com
290
291 mips --target=mips-elf ,-Werror
292
293 mn10300 --target=mn10300-elf broken
294 (sim/ dies with make -j)
295 Michael Snyder Michael.Snyder@access-company.com
296
297 ms1 --target=ms1-elf ,-Werror
298 Kevin Buettner kevinb@redhat.com
299
300 ns32k Deleted
301
302 pa --target=hppa-elf ,-Werror
303
304 powerpc --target=powerpc-eabi ,-Werror
305
306 s390 --target=s390-linux-gnu ,-Werror
307
308 score --target=score-elf
309 Qinwei qinwei@sunnorth.com.cn
310
311 sh --target=sh-elf ,-Werror
312 --target=sh64-elf ,-Werror
313
314 sparc --target=sparc64-solaris2.10 ,-Werror
315 (--target=sparc-elf broken)
316
317 spu --target=spu-elf ,-Werror
318 Ulrich Weigand uweigand@de.ibm.com
319
320 v850 --target=v850-elf ,-Werror
321
322 vax --target=vax-netbsd ,-Werror
323
324 x86-64 --target=x86_64-linux-gnu ,-Werror
325
326 xstormy16 --target=xstormy16-elf
327 Corinna Vinschen vinschen@redhat.com
328
329 xtensa --target=xtensa-elf
330 Maxim Grigoriev maxim2405@gmail.com
331
332 All developers recognized by this file can make arbitrary changes to
333 OBSOLETE targets.
334
335 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
336 above targets.
337
338
339 Host/Native:
340
341 The Native maintainer is responsible for target specific native
342 support - typically shared libraries and quirks to procfs/ptrace/...
343 The Native maintainer works with the Arch and Core maintainers when
344 resolving more generic problems.
345
346 The host maintainer ensures that gdb can be built as a cross debugger on
347 their platform.
348
349 AIX Joel Brobecker brobecker@adacore.com
350
351 djgpp native Eli Zaretskii eliz@gnu.org
352 GNU Hurd Alfred M. Szmidt ams@gnu.org
353 MS Windows (NT, '00, 9x, Me, XP) host & native
354 Chris Faylor cgf@alum.bu.edu
355 GNU/Linux/x86 native & host
356 Mark Kettenis kettenis@gnu.org
357 GNU/Linux MIPS native & host
358 Daniel Jacobowitz dan@debian.org
359 GNU/Linux m68k Andreas Schwab schwab@suse.de
360 FreeBSD native & host Mark Kettenis kettenis@gnu.org
361
362
363
364 Core: Generic components used by all of GDB
365
366 tracing Michael Snyder Michael.Snyder@access-company.com
367 threads Michael Snyder Michael.Snyder@access-company.com
368 Mark Kettenis kettenis@gnu.org
369 language support
370 C++ Daniel Jacobowitz dan@debian.org
371 Objective C support Adam Fedor fedor@gnu.org
372 shared libs Kevin Buettner kevinb@redhat.com
373
374 documentation Eli Zaretskii eliz@gnu.org
375 (including NEWS)
376 testsuite
377 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
378 threads (gdb.threads) Michael Snyder Michael.Snyder@access-company.com
379 trace (gdb.trace) Michael Snyder Michael.Snyder@access-company.com
380
381
382 UI: External (user) interfaces.
383
384 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
385 Keith Seitz keiths@redhat.com
386 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
387
388
389 Misc:
390
391 gdb/gdbserver Daniel Jacobowitz dan@debian.org
392
393 Makefile.in, configure* ALL
394
395 mmalloc/ ALL Host maintainers
396
397 sim/ See sim/MAINTAINERS
398
399 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
400 ALL
401 Host maintainers (host dependant parts)
402 (but get your changes into the master version)
403
404 tcl/ tk/ itcl/ ALL
405
406
407 Authorized Committers
408 ---------------------
409
410 These are developers working on particular areas of GDB, who are trusted to
411 commit their own (or other developers') patches in those areas without
412 further review from a Global Maintainer or Responsible Maintainer. They are
413 under no obligation to review posted patches - but, of course, are invited
414 to do so!
415
416 PowerPC Andrew Cagney cagney@gnu.org
417 CRIS Hans-Peter Nilsson hp@bitrange.com
418 IA64 Jeff Johnston jjohnstn@redhat.com
419 MIPS Joel Brobecker brobecker@adacore.com
420 m32r Kei Sakamoto sakamoto.kei@renesas.com
421 PowerPC Kevin Buettner kevinb@redhat.com
422 CRIS Orjan Friberg orjanf@axis.com
423 HPPA Randolph Chung tausq@debian.org
424 S390 Ulrich Weigand uweigand@de.ibm.com
425 djgpp DJ Delorie dj@delorie.com
426 [Please use this address to contact DJ about DJGPP]
427 tui Stephane Carrez stcarrez@nerim.fr
428 ia64 Kevin Buettner kevinb@redhat.com
429 AIX Kevin Buettner kevinb@redhat.com
430 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
431 gdb.java tests Anthony Green green@redhat.com
432 FreeBSD native & host David O'Brien obrien@freebsd.org
433 event loop Elena Zannoni ezannoni@redhat.com
434 generic symtabs Elena Zannoni ezannoni@redhat.com
435 dwarf readers Elena Zannoni ezannoni@redhat.com
436 elf reader Elena Zannoni ezannoni@redhat.com
437 stabs reader Elena Zannoni ezannoni@redhat.com
438 readline/ Elena Zannoni ezannoni@redhat.com
439 NetBSD native & host Jason Thorpe thorpej@netbsd.org
440 Pascal support Pierre Muller muller@sources.redhat.com
441 avr Theodore A. Roth troth@openavr.org
442 Modula-2 support Gaius Mulley gaius@glam.ac.uk
443
444
445 Write After Approval
446 (alphabetic)
447
448 To get recommended for the Write After Approval list you need a valid
449 FSF assignment and have submitted one good patch.
450
451 Pedro Alves pedro_alves@portugalmail.pt
452 David Anderson davea@sgi.com
453 John David Anglin dave.anglin@nrc-cnrc.gc.ca
454 Shrinivas Atre shrinivasa@kpitcummins.com
455 Scott Bambrough scottb@netwinder.org
456 Jan Beulich jbeulich@novell.com
457 Jim Blandy jimb@codesourcery.com
458 Philip Blundell philb@gnu.org
459 Per Bothner per@bothner.com
460 Joel Brobecker brobecker@adacore.com
461 Dave Brolley brolley@redhat.com
462 Paul Brook paul@codesourcery.com
463 Julian Brown julian@codesourcery.com
464 Kevin Buettner kevinb@redhat.com
465 Andrew Cagney cagney@gnu.org
466 David Carlton carlton@bactrian.org
467 Stephane Carrez stcarrez@nerim.fr
468 Michael Chastain mec.gnu@mindspring.com
469 Eric Christopher echristo@apple.com
470 Randolph Chung tausq@debian.org
471 Nick Clifton nickc@redhat.com
472 J.T. Conklin jtc@acorntoolworks.com
473 Brendan Conoboy blc@redhat.com
474 Ludovic Courtès ludo@gnu.org
475 DJ Delorie dj@redhat.com
476 Philippe De Muyter phdm@macqel.be
477 Dhananjay Deshpande dhananjayd@kpitcummins.com
478 Klee Dienes kdienes@apple.com
479 Gabriel Dos Reis gdr@integrable-solutions.net
480 Richard Earnshaw rearnsha@arm.com
481 Steve Ellcey sje@cup.hp.com
482 Frank Ch. Eigler fche@redhat.com
483 Ben Elliston bje@gnu.org
484 Adam Fedor fedor@gnu.org
485 Fred Fish fnf@ninemoons.com
486 Brian Ford ford@vss.fsi.com
487 Orjan Friberg orjanf@axis.com
488 Nathan Froyd froydnj@codesourcery.com
489 Gary Funck gary@intrepid.com
490 Paul Gilliam pgilliam@us.ibm.com
491 Raoul Gough RaoulGough@yahoo.co.uk
492 Anthony Green green@redhat.com
493 Matthew Green mrg@eterna.com.au
494 Maxim Grigoriev maxim2405@gmail.com
495 Jerome Guitton guitton@act-europe.fr
496 Ben Harris bjh21@netbsd.org
497 Richard Henderson rth@redhat.com
498 Aldy Hernandez aldyh@redhat.com
499 Paul Hilfinger hilfinger@gnat.com
500 Matt Hiller hiller@redhat.com
501 Kazu Hirata kazu@cs.umass.edu
502 Jeff Holcomb jeffh@redhat.com
503 Don Howard dhoward@redhat.com
504 Martin Hunt hunt@redhat.com
505 Jim Ingham jingham@apple.com
506 Baurzhan Ismagulov ibr@radix50.net
507 Manoj Iyer manjo@austin.ibm.com
508 Daniel Jacobowitz dan@debian.org
509 Andreas Jaeger aj@suse.de
510 Jeff Johnston jjohnstn@redhat.com
511 Geoff Keating geoffk@redhat.com
512 Mark Kettenis kettenis@gnu.org
513 Jim Kingdon kingdon@panix.com
514 Jan Kratochvil jan.kratochvil@redhat.com
515 Jonathan Larmour jlarmour@redhat.co.uk
516 Jeff Law law@redhat.com
517 David Lecomber david@streamline-computing.com
518 Robert Lipe rjl@sco.com
519 H.J. Lu hjl@lucon.org
520 Michal Ludvig mludvig@suse.cz
521 Glen McCready gkm@redhat.com
522 Greg McGary greg@mcgary.org
523 Roland McGrath roland@redhat.com
524 Bryce McKinlay mckinlay@redhat.com
525 Jason Merrill jason@redhat.com
526 David S. Miller davem@redhat.com
527 Mark Mitchell mark@codesourcery.com
528 Marko Mlinar markom@opencores.org
529 Alan Modra amodra@bigpond.net.au
530 Jason Molenda jmolenda@apple.com
531 Pierre Muller muller@sources.redhat.com
532 Gaius Mulley gaius@glam.ac.uk
533 Joseph Myers joseph@codesourcery.com
534 Fernando Nasser fnasser@redhat.com
535 Adam Nemet anemet@caviumnetworks.com
536 Nathanael Nerode neroden@gcc.gnu.org
537 Hans-Peter Nilsson hp@bitrange.com
538 David O'Brien obrien@freebsd.org
539 Alexandre Oliva aoliva@redhat.com
540 Denis Pilat denis.pilat@st.com
541 Vladimir Prus vladimir@codesourcery.com
542 Qinwei qinwei@sunnorth.com.cn
543 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
544 Frederic Riss frederic.riss@st.com
545 Tom Rix trix@redhat.com
546 Nick Roberts nickrob@snap.net.nz
547 Bob Rossi bob_rossi@cox.net
548 Theodore A. Roth troth@openavr.org
549 Ian Roxborough irox@redhat.com
550 Maciej W. Rozycki macro@linux-mips.org
551 Grace Sainsbury graces@redhat.com
552 Kei Sakamoto sakamoto.kei@renesas.com
553 Mark Salter msalter@redhat.com
554 Richard Sandiford richard@codesourcery.com
555 Peter Schauer Peter.Schauer@mytum.de
556 Andreas Schwab schwab@suse.de
557 Keith Seitz keiths@redhat.com
558 Stan Shebs shebs@mozilla.com
559 Mark Shinwell shinwell@codesourcery.com
560 Aidan Skinner aidan@velvet.net
561 Jiri Smid smid@suse.cz
562 David Smith dsmith@redhat.com
563 Stephen P. Smith ischis2@cox.net
564 Jackie Smith Cashion jsmith@redhat.com
565 Michael Snyder Michael.Snyder@access-company.com
566 Petr Sorfa petrs@caldera.com
567 Andrew Stubbs andrew.stubbs@st.com
568 Ian Lance Taylor ian@airs.com
569 Gary Thomas gthomas@redhat.com
570 Jason Thorpe thorpej@netbsd.org
571 Caroline Tice ctice@apple.com
572 Tom Tromey tromey@redhat.com
573 David Ung davidu@mips.com
574 D Venkatasubramanian dvenkat@noida.hcltech.com
575 Corinna Vinschen vinschen@redhat.com
576 Keith Walker keith.walker@arm.com
577 Kris Warkentin kewarken@qnx.com
578 Ulrich Weigand uweigand@de.ibm.com
579 Nathan Williams nathanw@wasabisystems.com
580 Bob Wilson bob.wilson@acm.org
581 Jim Wilson wilson@specifixinc.com
582 Elena Zannoni ezannoni@redhat.com
583 Eli Zaretskii eliz@gnu.org
584 Wu Zhou woodzltc@cn.ibm.com
585 Yoshinori Sato ysato@users.sourceforge.jp
586
587
588 Past Maintainers
589
590 Whenever removing yourself, or someone else, from this file, consider
591 listing their areas of development here for posterity.
592
593 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
594 Jeff Law (hppa) law at cygnus dot com
595 Daniel Berlin (C++ support) dan at cgsoftware dot com
596 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
597 David Taylor (d10v, sparc, utils, defs,
598 expression evaluator, language support) taylor at candd dot org
599 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
600 Frank Ch. Eigler (sim) fche at redhat dot com
601 Per Bothner (Java) per at bothner dot com
602 Anthony Green (Java) green at redhat dot com
603 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
604 Mark Salter (testsuite/lib+config) msalter at redhat dot com
605 Jim Kingdon (web pages) kingdon at panix dot com
606 Jim Ingham (gdbtk, libgui) jingham at apple dot com
607 Mark Kettenis (hurd native) kettenis at gnu dot org
608 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
609 Robert Lipe (SCO/Unixware) rjl at sco dot com
610 Peter Schauer (global, AIX, xcoffsolib,
611 Solaris/x86) Peter.Schauer at mytum dot de
612 Scott Bambrough (ARM) scottb at netwinder dot org
613 Philippe De Muyter (coff) phdm at macqel dot be
614 Michael Chastain (testsuite) mec.gnu at mindspring dot com
615
616
617
618 Folks that have been caught up in a paper trail:
619
620 David Carlton carlton@bactrian.org
621
622 ;; Local Variables:
623 ;; coding: utf-8
624 ;; End:
This page took 0.042502 seconds and 4 git commands to generate.