MAINTAINERS 28 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779
  1. GDB Maintainers
  2. ===============
  3. Overview
  4. --------
  5. This file describes different groups of people who are, together, the
  6. maintainers and developers of the GDB project. Don't worry - it sounds
  7. more complicated than it really is.
  8. There are four groups of GDB developers, covering the patch development and
  9. review process:
  10. - The Global Maintainers.
  11. These are the developers in charge of most daily development. They
  12. have wide authority to apply and reject patches, but defer to the
  13. Responsible Maintainers (see below) within their spheres of
  14. responsibility.
  15. - The Responsible Maintainers.
  16. These are developers who have expertise and interest in a particular
  17. area of GDB, who are generally available to review patches, and who
  18. prefer to enforce a single vision within their areas.
  19. - The Authorized Committers.
  20. These are developers who are trusted to make changes within a specific
  21. area of GDB without additional oversight.
  22. - The Write After Approval Maintainers.
  23. These are developers who have write access to the GDB source tree. They
  24. can check in their own changes once a developer with the appropriate
  25. authority has approved the changes; they can also apply the Obvious
  26. Fix Rule (below).
  27. All maintainers are encouraged to post major patches to the gdb-patches
  28. mailing list for comments, even if they have the authority to commit the
  29. patch without review from another maintainer. This especially includes
  30. patches which change internal interfaces (e.g. global functions, data
  31. structures) or external interfaces (e.g. user, remote, MI, et cetera).
  32. The term "review" is used in this file to describe several kinds of feedback
  33. from a maintainer: approval, rejection, and requests for changes or
  34. clarification with the intention of approving a revised version. Review is
  35. a privilege and/or responsibility of various positions among the GDB
  36. Maintainers. Of course, anyone - whether they hold a position but not the
  37. relevant one for a particular patch, or are just following along on the
  38. mailing lists for fun, or anything in between - may suggest changes or
  39. ask questions about a patch!
  40. There's also a couple of other people who play special roles in the GDB
  41. community, separately from the patch process:
  42. - The Official FSF-appointed GDB Maintainers.
  43. These maintainers are the ones who take the overall responsibility
  44. for GDB, as a package of the GNU project. Other GDB contributors
  45. work under the official maintainers' supervision. They have final
  46. and overriding authority for all GDB-related decisions, including
  47. anything described in this file. As individuals, they may or not
  48. be generally involved in day-to-day development.
  49. - The Release Manager.
  50. This developer is in charge of making new releases of GDB.
  51. - The Patch Champions.
  52. These volunteers make sure that no contribution is overlooked or
  53. forgotten.
  54. Most changes to the list of maintainers in this file are handled by
  55. consensus among the global maintainers and any other involved parties.
  56. In cases where consensus can not be reached, the global maintainers may
  57. ask the official FSF-appointed GDB maintainers for a final decision.
  58. The Obvious Fix Rule
  59. --------------------
  60. All maintainers listed in this file, including the Write After Approval
  61. developers, are allowed to check in obvious fixes.
  62. An "obvious fix" means that there is no possibility that anyone will
  63. disagree with the change.
  64. A good mental test is "will the person who hates my work the most be
  65. able to find fault with the change" - if so, then it's not obvious and
  66. needs to be posted first. :-)
  67. Something like changing or bypassing an interface is _not_ an obvious
  68. fix, since such a change without discussion will result in
  69. instantaneous and loud complaints.
  70. For documentation changes, about the only kind of fix that is obvious
  71. is correction of a typo or bad English usage.
  72. The Official FSF-appointed GDB Maintainers
  73. ------------------------------------------
  74. These maintainers as a group have final authority for all GDB-related
  75. topics; they may make whatever changes that they deem necessary, or
  76. that the FSF requests.
  77. The current official FSF-appointed GDB maintainers are listed below,
  78. in alphabetical order. Their affiliations are provided for reference
  79. only - their maintainership status is individual and not through their
  80. affiliation, and they act on behalf of the GNU project.
  81. Pedro Alves
  82. Joel Brobecker (AdaCore)
  83. Doug Evans (Google)
  84. Eli Zaretskii
  85. Global Maintainers
  86. ------------------
  87. The global maintainers may review and commit any change to GDB, except in
  88. areas with a Responsible Maintainer available. For major changes, or
  89. changes to areas with other active developers, global maintainers are
  90. strongly encouraged to post their own patches for feedback before
  91. committing.
  92. The global maintainers are responsible for reviewing patches to any area
  93. for which no Responsible Maintainer is listed.
  94. Global maintainers also have the authority to revert patches which should
  95. not have been applied, e.g. patches which were not approved, controversial
  96. patches committed under the Obvious Fix Rule, patches with important bugs
  97. that can't be immediately fixed, or patches which go against an accepted and
  98. documented roadmap for GDB development. Any global maintainer may request
  99. the reversion of a patch. If no global maintainer, or responsible
  100. maintainer in the affected areas, supports the patch (except for the
  101. maintainer who originally committed it), then after 48 hours the maintainer
  102. who called for the reversion may revert the patch.
  103. No one may reapply a reverted patch without the agreement of the maintainer
  104. who reverted it, or bringing the issue to the official FSF-appointed
  105. GDB maintainers for discussion.
  106. At the moment there are no documented roadmaps for GDB development; in the
  107. future, if there are, a reference to the list will be included here.
  108. The current global maintainers are (in alphabetical order):
  109. Pedro Alves pedro@palves.net
  110. Joel Brobecker brobecker@adacore.com
  111. Kevin Buettner kevinb@redhat.com
  112. Andrew Burgess aburgess@redhat.com
  113. Doug Evans dje@google.com
  114. Simon Marchi simon.marchi@polymtl.ca
  115. Yao Qi qiyao@sourceware.org
  116. Tom Tromey tom@tromey.com
  117. Tom de Vries tdevries@suse.de
  118. Ulrich Weigand Ulrich.Weigand@de.ibm.com
  119. Eli Zaretskii eliz@gnu.org
  120. Release Manager
  121. ---------------
  122. The current release manager is: Joel Brobecker <brobecker@adacore.com>
  123. His responsibilities are:
  124. * organizing, scheduling, and managing releases of GDB.
  125. * deciding the approval and commit policies for release branches,
  126. and can change them as needed.
  127. Patch Champions
  128. ---------------
  129. These volunteers track all patches submitted to the gdb-patches list. They
  130. endeavor to prevent any posted patch from being overlooked; work with
  131. contributors to meet GDB's coding style and general requirements, along with
  132. FSF copyright assignments; remind (ping) responsible maintainers to review
  133. patches; and ensure that contributors are given credit.
  134. Current patch champions (in alphabetical order):
  135. <none>
  136. Responsible Maintainers
  137. -----------------------
  138. These developers have agreed to review patches in specific areas of GDB, in
  139. which they have knowledge and experience. These areas are generally broad;
  140. the role of a responsible maintainer is to provide coherent and cohesive
  141. structure within their area of GDB, to assure that patches from many
  142. different contributors all work together for the best results.
  143. Global maintainers will defer to responsible maintainers within their areas,
  144. as long as the responsible maintainer is active. Active means that
  145. responsible maintainers agree to review submitted patches in their area
  146. promptly; patches and followups should generally be answered within a week.
  147. If a responsible maintainer is interested in reviewing a patch but will not
  148. have time within a week of posting, the maintainer should send an
  149. acknowledgement of the patch to the gdb-patches mailing list, and
  150. plan to follow up with a review within a month. These deadlines are for
  151. initial responses to a patch - if the maintainer has suggestions
  152. or questions, it may take an extended discussion before the patch
  153. is ready to commit. There are no written requirements for discussion,
  154. but maintainers are asked to be responsive.
  155. If a responsible maintainer misses these deadlines occasionally (e.g.
  156. vacation or unexpected workload), it's not a disaster - any global
  157. maintainer may step in to review the patch. But sometimes life intervenes
  158. more permanently, and a maintainer may no longer have time for these duties.
  159. When this happens, he or she should step down (either into the Authorized
  160. Committers section if still interested in the area, or simply removed from
  161. the list of Responsible Maintainers if not).
  162. If a responsible maintainer is unresponsive for an extended period of time
  163. without stepping down, please contact the Global Maintainers; they will try
  164. to contact the maintainer directly and fix the problem - potentially by
  165. removing that maintainer from their listed position.
  166. If there are several maintainers for a given domain then any one of them
  167. may review a submitted patch.
  168. Target Instruction Set Architectures:
  169. The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
  170. (Operating System / Application Binary Interface) issues including CPU
  171. variants.
  172. The Target/Architecture maintainer works with the host maintainer when
  173. resolving build issues. The Target/Architecture maintainer works with
  174. the native maintainer when resolving ABI issues.
  175. aarch64 --target=aarch64-elf ,-Werror
  176. Alan Hayward alan.hayward@arm.com
  177. Luis Machado luis.machado@arm.com
  178. alpha --target=alpha-elf ,-Werror
  179. arc --target=arc-elf
  180. Shahab Vahedi shahab@synopsys.com
  181. arm --target=arm-elf ,-Werror
  182. Alan Hayward alan.hayward@arm.com
  183. Luis Machado luis.machado@arm.com
  184. avr --target=avr ,-Werror
  185. bpf --target=bpf-unknown-none
  186. Jose E. Marchesi jose.marchesi@oracle.com
  187. cris --target=cris-elf ,-Werror ,
  188. (sim does not build with -Werror)
  189. frv --target=frv-elf ,-Werror
  190. h8300 --target=h8300-elf ,-Werror
  191. i386 --target=i386-elf ,-Werror
  192. ia64 --target=ia64-linux-gnu ,-Werror
  193. (--target=ia64-elf broken)
  194. lm32 --target=lm32-elf ,-Werror
  195. loongarch --target=loongarch32-elf ,-Werror
  196. --target=loongarch64-elf ,-Werror
  197. Tiezhu Yang yangtiezhu@loongson.cn
  198. m32c --target=m32c-elf ,-Werror
  199. m32r --target=m32r-elf ,-Werror
  200. m68hc11 --target=m68hc11-elf ,-Werror ,
  201. m68k --target=m68k-elf ,-Werror
  202. mcore Deleted
  203. mep --target=mep-elf ,-Werror
  204. Kevin Buettner kevinb@redhat.com
  205. microblaze --target=microblaze-xilinx-elf ,-Werror
  206. --target=microblaze-linux-gnu ,-Werror
  207. Michael Eager eager@eagercon.com
  208. mips I-IV --target=mips-elf ,-Werror
  209. Maciej W. Rozycki macro@orcam.me.uk
  210. mn10300 --target=mn10300-elf broken
  211. (sim/ dies with make -j)
  212. moxie --target=moxie-elf ,-Werror
  213. Anthony Green green@moxielogic.com
  214. ms1 Deleted
  215. nios2 --target=nios2-elf ,-Werror
  216. --target=nios2-linux-gnu ,-Werror
  217. Yao Qi qiyao@sourceware.org
  218. ns32k Deleted
  219. or1k --target=or1k-elf ,-Werror
  220. Stafford Horne shorne@gmail.com
  221. pa --target=hppa-elf ,-Werror
  222. powerpc --target=powerpc-eabi ,-Werror
  223. riscv --target=riscv32-elf ,-Werror
  224. --target=riscv64-elf ,-Werror
  225. Andrew Burgess aburgess@redhat.com
  226. Palmer Dabbelt palmer@dabbelt.com
  227. rl78 --target=rl78-elf ,-Werror
  228. rx --target=rx-elf ,-Werror
  229. s390 --target=s390-linux-gnu ,-Werror
  230. Andreas Arnez arnez@linux.ibm.com
  231. score --target=score-elf
  232. sh --target=sh-elf ,-Werror
  233. sparc --target=sparcv9-solaris2.11 ,-Werror
  234. (--target=sparc-elf broken)
  235. tic6x --target=tic6x-elf ,-Werror
  236. Yao Qi qiyao@sourceware.org
  237. v850 --target=v850-elf ,-Werror
  238. vax --target=vax-netbsd ,-Werror
  239. x86-64 --target=x86_64-linux-gnu ,-Werror
  240. xstormy16 --target=xstormy16-elf
  241. xtensa --target=xtensa-elf
  242. All developers recognized by this file can make arbitrary changes to
  243. OBSOLETE targets.
  244. The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
  245. above targets.
  246. Host/Native:
  247. The Native maintainer is responsible for target specific native
  248. support - typically shared libraries and quirks to procfs/ptrace/...
  249. The Native maintainer works with the Arch and Core maintainers when
  250. resolving more generic problems.
  251. The host maintainer ensures that gdb can be built as a cross debugger on
  252. their platform.
  253. Darwin Tristan Gingold tgingold@free.fr
  254. djgpp native Eli Zaretskii eliz@gnu.org
  255. FreeBSD John Baldwin jhb@freebsd.org
  256. GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
  257. Solaris Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
  258. Core: Generic components used by all of GDB
  259. linespec Keith Seitz keiths@redhat.com
  260. language support
  261. Ada Joel Brobecker brobecker@adacore.com
  262. D Iain Buclaw ibuclaw@gdcproject.org
  263. Rust Tom Tromey tom@tromey.com
  264. shared libs Kevin Buettner kevinb@redhat.com
  265. MI interface Vladimir Prus vladimir@codesourcery.com
  266. documentation Eli Zaretskii eliz@gnu.org
  267. (including NEWS)
  268. testsuite
  269. gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
  270. SystemTap Sergio Durigan Junior sergiodj@sergiodj.net
  271. Reverse debugging / Record and Replay / Tracing:
  272. record btrace Markus T. Metzger markus.t.metzger@intel.com
  273. UI: External (user) interfaces.
  274. gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
  275. Keith Seitz keiths@redhat.com
  276. libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
  277. Misc:
  278. gdb/gdbserver Daniel Jacobowitz drow@false.org
  279. Makefile.in, configure* ALL
  280. mmalloc/ ALL Host maintainers
  281. sim/ See sim/MAINTAINERS
  282. readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
  283. ALL
  284. Host maintainers (host dependant parts)
  285. (but get your changes into the master version)
  286. tcl/ tk/ itcl/ ALL
  287. contrib/ari Pierre Muller muller@sourceware.org
  288. Authorized Committers
  289. ---------------------
  290. These are developers working on particular areas of GDB, who are trusted to
  291. commit their own (or other developers') patches in those areas without
  292. further review from a Global Maintainer or Responsible Maintainer. They are
  293. under no obligation to review posted patches - but, of course, are invited
  294. to do so!
  295. ARM Richard Earnshaw rearnsha@arm.com
  296. Blackfin Mike Frysinger vapier@gentoo.org
  297. CRIS Hans-Peter Nilsson hp@axis.com
  298. IA64 Jeff Johnston jjohnstn@redhat.com
  299. MIPS Joel Brobecker brobecker@adacore.com
  300. PowerPC Kevin Buettner kevinb@redhat.com
  301. S390 Ulrich Weigand uweigand@de.ibm.com
  302. djgpp DJ Delorie dj@delorie.com
  303. [Please use this address to contact DJ about DJGPP]
  304. ia64 Kevin Buettner kevinb@redhat.com
  305. AIX Kevin Buettner kevinb@redhat.com
  306. GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
  307. Pascal support Pierre Muller muller@sourceware.org
  308. Write After Approval
  309. (alphabetic)
  310. To get recommended for the Write After Approval list you need a valid
  311. FSF assignment and have submitted one good patch.
  312. Tankut Baris Aktemur tankut.baris.aktemur@intel.com
  313. Mihails Strasuns mihails.strasuns@intel.com
  314. David Anderson davea@sgi.com
  315. John David Anglin dave.anglin@nrc-cnrc.gc.ca
  316. Andreas Arnez arnez@linux.ibm.com
  317. Shrinivas Atre shrinivasa@kpitcummins.com
  318. Sterling Augustine saugustine@google.com
  319. John Baldwin jhb@freebsd.org
  320. Scott Bambrough scottb@netwinder.org
  321. Marco Barisione mbarisione@undo.io
  322. Thiago Jung Bauermann bauerman@br.ibm.com
  323. Jon Beniston jon@beniston.com
  324. Gary Benson gbenson@redhat.com
  325. Gabriel Krisman Bertazi gabriel@krisman.be
  326. Jan Beulich jbeulich@novell.com
  327. Christian Biesinger cbiesinger@google.com
  328. Anton Blanchard anton@samba.org
  329. Jim Blandy jimb@codesourcery.com
  330. David Blaikie dblaikie@gmail.com
  331. Philip Blundell philb@gnu.org
  332. Eric Botcazou ebotcazou@libertysurf.fr
  333. Per Bothner per@bothner.com
  334. Don Breazeal donb@codesourcery.com
  335. Joel Brobecker brobecker@adacore.com
  336. Dave Brolley brolley@redhat.com
  337. Samuel Bronson naesten@gmail.com
  338. Paul Brook paul@codesourcery.com
  339. Julian Brown julian@codesourcery.com
  340. Iain Buclaw ibuclaw@gdcproject.org
  341. Kevin Buettner kevinb@redhat.com
  342. Andrew Burgess aburgess@redhat.com
  343. David Carlton carlton@bactrian.org
  344. Stephane Carrez Stephane.Carrez@gmail.com
  345. Michael Chastain mec.gnu@mindspring.com
  346. Renquan Cheng crq@gcc.gnu.org
  347. Eric Christopher echristo@apple.com
  348. Randolph Chung tausq@debian.org
  349. Nick Clifton nickc@redhat.com
  350. J.T. Conklin jtc@acorntoolworks.com
  351. Brendan Conoboy blc@redhat.com
  352. Ludovic Courtès ludo@gnu.org
  353. Tiago Stürmer Daitx tdaitx@linux.vnet.ibm.com
  354. Sanjoy Das sanjoy@playingwithpointers.com
  355. Jean-Charles Delay delay@adacore.com
  356. DJ Delorie dj@redhat.com
  357. Chris Demetriou cgd@google.com
  358. Philippe De Muyter phdm@macqel.be
  359. Dhananjay Deshpande dhananjayd@kpitcummins.com
  360. Markus Deuling deuling@de.ibm.com
  361. Klee Dienes kdienes@apple.com
  362. Hannes Domani ssbssa@yahoo.de
  363. Gabriel Dos Reis gdr@integrable-solutions.net
  364. Sergio Durigan Junior sergiodj@sergiodj.net
  365. Michael Eager eager@eagercon.com
  366. Richard Earnshaw rearnsha@arm.com
  367. Bernd Edlinger bernd.edlinger@hotmail.de
  368. Steve Ellcey sje@cup.hp.com
  369. Frank Ch. Eigler fche@redhat.com
  370. Ben Elliston bje@gnu.org
  371. Doug Evans dje@google.com
  372. Adam Fedor fedor@gnu.org
  373. Max Filippov jcmvbkbc@gmail.com
  374. Brian Ford ford@vss.fsi.com
  375. Matthew Fortune matthew.fortune@imgtec.com
  376. Pedro Franco de Carvalho pedromfc@linux.vnet.ibm.com
  377. Orjan Friberg orjanf@axis.com
  378. Andreas From andreas.from@ericsson.com
  379. Nathan Froyd froydnj@codesourcery.com
  380. Mike Frysinger vapier@gentoo.org
  381. Gary Funck gary@intrepid.com
  382. Martin Galvan martingalvan@sourceware.org
  383. Chen Gang gang.chen.5i5j@gmail.com
  384. Mircea Gherzan mircea.gherzan@intel.com
  385. Paul Gilliam pgilliam@us.ibm.com
  386. Tristan Gingold tgingold@free.fr
  387. Anton Gorenkov xgsa@yandex.ru
  388. Raoul Gough RaoulGough@yahoo.co.uk
  389. Anthony Green green@redhat.com
  390. Matthew Green mrg@eterna.com.au
  391. Matthew Gretton-Dann matthew.gretton-dann@arm.com
  392. Maxim Grigoriev maxim2405@gmail.com
  393. Jerome Guitton guitton@act-europe.fr
  394. Alexandra Hájková ahajkova@redhat.com
  395. Ben Harris bjh21@netbsd.org
  396. Alan Hayward alan.hayward@arm.com
  397. Bernhard Heckel heckel_bernhard@web.de
  398. Richard Henderson rth@redhat.com
  399. Aldy Hernandez aldyh@redhat.com
  400. Paul Hilfinger hilfingr@eecs.berkeley.edu
  401. Matt Hiller hiller@redhat.com
  402. Kazu Hirata kazu@cs.umass.edu
  403. James Hogan james.hogan@imgtec.com
  404. Jeff Holcomb jeffh@redhat.com
  405. Stafford Horne shorne@gmail.com
  406. Magne Hov mhov@undo.io
  407. Don Howard dhoward@redhat.com
  408. Nick Hudson nick.hudson@dsl.pipex.com
  409. Martin Hunt hunt@redhat.com
  410. Meador Inge meadori@codesourcery.com
  411. Jim Ingham jingham@apple.com
  412. Baurzhan Ismagulov ibr@radix50.net
  413. Manoj Iyer manjo@austin.ibm.com
  414. Daniel Jacobowitz drow@false.org
  415. Andreas Jaeger aj@suse.de
  416. Janis Johnson janisjo@codesourcery.com
  417. Jeff Johnston jjohnstn@redhat.com
  418. Ruslan Kabatsayev b7.10110111@gmail.com
  419. Geoff Keating geoffk@redhat.com
  420. Nils-Christian Kempke nils-christian.kempke@intel.com
  421. Mark Kettenis kettenis@gnu.org
  422. Marc Khouzam marc.khouzam@ericsson.com
  423. Toshihito Kikuchi k.toshihito@yahoo.de
  424. Jim Kingdon kingdon@panix.com
  425. Anton Kolesov anton.kolesov@synopsys.com
  426. Paul Koning paul_koning@dell.com
  427. Marcin Kościelnicki koriakin@0x04.net
  428. Jan Kratochvil jan.kratochvil@redhat.com
  429. Maxim Kuvyrkov maxim@kugelworks.com
  430. Pierre Langlois pierre.langlois@arm.com
  431. Jonathan Larmour jifl@ecoscentric.com
  432. Bruno Larsen blarsen@redhat.com
  433. Jeff Law law@redhat.com
  434. Justin Lebar justin.lebar@gmail.com
  435. David Lecomber david@streamline-computing.com
  436. Don Lee don.lee@sunplusct.com
  437. Enze Li lienze2010@hotmail.com
  438. Yan-Ting Lin currygt52@gmail.com
  439. Robert Lipe rjl@sco.com
  440. Lei Liu lei.liu2@windriver.com
  441. Sandra Loosemore sandra@codesourcery.com
  442. Carl Love cel@us.ibm.com
  443. H.J. Lu hjl.tools@gmail.com
  444. Michal Ludvig mludvig@suse.cz
  445. Edjunior B. Machado emachado@linux.vnet.ibm.com
  446. Luis Machado luis.machado@arm.com
  447. Jose E. Marchesi jose.marchesi@oracle.com
  448. Glen McCready gkm@redhat.com
  449. Greg McGary greg@mcgary.org
  450. Roland McGrath roland@hack.frob.com
  451. Bryce McKinlay mckinlay@redhat.com
  452. Jason Merrill jason@redhat.com
  453. Markus T. Metzger markus.t.metzger@intel.com
  454. David S. Miller davem@redhat.com
  455. Mark Mitchell mark@codesourcery.com
  456. Marko Mlinar markom@opencores.org
  457. Alan Modra amodra@gmail.com
  458. Fawzi Mohamed fawzi.mohamed@nokia.com
  459. Jason Molenda jmolenda@apple.com
  460. Chris Moller cmoller@redhat.com
  461. Phil Muldoon pmuldoon@redhat.com
  462. Pierre Muller muller@sourceware.org
  463. Gaius Mulley gaius@glam.ac.uk
  464. Masaki Muranaka monaka@monami-software.com
  465. Joseph Myers joseph@codesourcery.com
  466. Fernando Nasser fnasser@redhat.com
  467. Adam Nemet anemet@caviumnetworks.com
  468. Will Newton will.newton@linaro.org
  469. Nathanael Nerode neroden@gcc.gnu.org
  470. Hans-Peter Nilsson hp@bitrange.com
  471. David O'Brien obrien@freebsd.org
  472. Alexandre Oliva aoliva@redhat.com
  473. Rainer Orth ro@cebitec.uni-bielefeld.de
  474. Karen Osmond karen.osmond@gmail.com
  475. Pawandeep Oza oza.pawandeep@gmail.com
  476. Patrick Palka patrick@parcs.ath.cx
  477. Weimin Pan weimin.pan@oracle.com
  478. Denis Pilat denis.pilat@st.com
  479. Andrew Pinski apinski@cavium.com
  480. Kevin Pouget kevin.pouget@st.com
  481. Paul Pluzhnikov ppluzhnikov@google.com
  482. Marek Polacek mpolacek@redhat.com
  483. Siddhesh Poyarekar siddhesh@redhat.com
  484. Vladimir Prus vladimir@codesourcery.com
  485. Yao Qi qiyao@sourceware.org
  486. Qinwei qinwei@sunnorth.com.cn
  487. Ramana Radhakrishnan ramana.radhakrishnan@arm.com
  488. Siva Chandra Reddy sivachandra@google.com
  489. Matt Rice ratmice@gmail.com
  490. Frederic Riss frederic.riss@st.com
  491. Aleksandar Ristovski aristovski@qnx.com
  492. Tom Rix trix@redhat.com
  493. Nick Roberts nickrob@snap.net.nz
  494. Pierre-Marie de Rodat derodat@adacore.com
  495. Xavier Roirand roirand@adacore.com
  496. Bob Rossi bob_rossi@cox.net
  497. Theodore A. Roth troth@openavr.org
  498. Ian Roxborough irox@redhat.com
  499. Maciej W. Rozycki macro@orcam.me.uk
  500. Kamil Rytarowski n54@gmx.com
  501. Grace Sainsbury graces@redhat.com
  502. Kei Sakamoto sakamoto.kei@renesas.com
  503. Mark Salter msalter@redhat.com
  504. Richard Sandiford richard@codesourcery.com
  505. Iain Sandoe iain@codesourcery.com
  506. Peter Schauer Peter.Schauer@mytum.de
  507. Will Schmidt will_schmidt@vnet.ibm.com
  508. Andreas Schwab schwab@linux-m68k.org
  509. Thomas Schwinge tschwinge@gnu.org
  510. Keith Seitz keiths@redhat.com
  511. Carlos Eduardo Seo cseo@linux.vnet.ibm.com
  512. Ozkan Sezer sezeroz@gmail.com
  513. Alok Kumar Sharma AlokKumar.Sharma@amd.com
  514. Marcus Shawcroft marcus.shawcroft@arm.com
  515. Stan Shebs stanshebs@google.com
  516. Joel Sherrill joel.sherrill@oarcorp.com
  517. Mark Shinwell shinwell@codesourcery.com
  518. Craig Silverstein csilvers@google.com
  519. Lancelot Six lsix@lancelotsix.com
  520. Aidan Skinner aidan@velvet.net
  521. Jiri Smid smid@suse.cz
  522. Andrey Smirnov andrew.smirnov@gmail.com
  523. David Smith dsmith@redhat.com
  524. Stephen P. Smith ischis2@cox.net
  525. Jackie Smith Cashion jsmith@redhat.com
  526. Petr Sorfa petrs@caldera.com
  527. Andrew Stubbs ams@codesourcery.com
  528. Emi Suzuki emi-suzuki@tjsys.co.jp
  529. Alfred M. Szmidt ams@gnu.org
  530. Ali Tamur tamur@google.com
  531. David Taylor david.taylor@emc.com
  532. Ian Lance Taylor ian@airs.com
  533. Walfred Tedeschi walfred.tedeschi@intel.com
  534. Petr Tesarik ptesarik@suse.cz
  535. Samuel Thibault samuel.thibault@ens-lyon.org
  536. Gary Thomas gthomas@redhat.com
  537. Jason Thorpe thorpej@netbsd.org
  538. Caroline Tice ctice@apple.com
  539. Kai Tietz ktietz@redhat.com
  540. Andreas Tobler andreast@fgznet.ch
  541. Jon Turney jon.turney@dronecode.org.uk
  542. David Ung davidu@mips.com
  543. Shahab Vahedi shahab@synopsys.com
  544. D Venkatasubramanian dvenkat@noida.hcltech.com
  545. Corinna Vinschen vinschen@redhat.com
  546. Jan Vrany jan.vrany@fit.cvut.cz
  547. Sami Wagiaalla swagiaal@redhat.com
  548. Keith Walker keith.walker@arm.com
  549. Ricard Wanderlof ricardw@axis.com
  550. Jiong Wang jiong.wang@arm.com
  551. Wei-cheng Wang cole945@gmail.com
  552. Kris Warkentin kewarken@qnx.com
  553. Philippe Waroquiers philippe.waroquiers@skynet.be
  554. Ulrich Weigand uweigand@de.ibm.com
  555. Ken Werner ken.werner@de.ibm.com
  556. Tim Wiederhake tim.wiederhake@intel.com
  557. Mark Wielaard mark@klomp.org
  558. Felix Willgerodt felix.willgerodt@intel.com
  559. Nathan Williams nathanw@wasabisystems.com
  560. Bob Wilson bob.wilson@acm.org
  561. Jim Wilson wilson@tuliptree.org
  562. Andy Wingo wingo@igalia.com
  563. Mike Wrighton wrighton@codesourcery.com
  564. Tiezhu Yang yangtiezhu@loongson.cn
  565. Kwok Cheung Yeung kcy@codesourcery.com
  566. Elena Zannoni ezannoni@gmail.com
  567. Eli Zaretskii eliz@gnu.org
  568. Jie Zhang jzhang918@gmail.com
  569. Wu Zhou woodzltc@cn.ibm.com
  570. Yoshinori Sato ysato@users.sourceforge.jp
  571. Hui Zhu teawater@gmail.com
  572. Khoo Yit Phang khooyp@cs.umd.edu
  573. Rogerio Alves rcardoso@linux.ibm.com
  574. Past Maintainers
  575. Whenever removing yourself, or someone else, from this file, consider
  576. listing their areas of development here for posterity.
  577. Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
  578. Jeff Law (hppa) law at cygnus dot com
  579. Daniel Berlin (C++ support) dan at cgsoftware dot com
  580. Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
  581. David Taylor (d10v, sparc, utils, defs,
  582. expression evaluator, language support) taylor at candd dot org
  583. J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
  584. Frank Ch. Eigler (sim) fche at redhat dot com
  585. Per Bothner (Java) per at bothner dot com
  586. Anthony Green (Java) green at redhat dot com
  587. Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
  588. Mark Salter (testsuite/lib+config) msalter at redhat dot com
  589. Jim Kingdon (web pages) kingdon at panix dot com
  590. Jim Ingham (gdbtk, libgui) jingham at apple dot com
  591. Mark Kettenis (global, i386-elf, m88k-openbsd,
  592. GNU/Linux x86, FreeBSD, hurd native, threads) kettenis at gnu dot org
  593. Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
  594. Robert Lipe (SCO/Unixware) rjl at sco dot com
  595. Peter Schauer (global, AIX, xcoffsolib,
  596. Solaris/x86) Peter.Schauer at mytum dot de
  597. Scott Bambrough (ARM) scottb at netwinder dot org
  598. Philippe De Muyter (coff) phdm at macqel dot be
  599. Michael Chastain (testsuite) mec.gnu at mindspring dot com
  600. Fred Fish (global)
  601. Jim Blandy (global) jimb@red-bean.com
  602. Michael Snyder (global)
  603. Christopher Faylor (MS Windows, host & native)
  604. Daniel Jacobowitz (global, GNU/Linux MIPS,
  605. C++, GDBserver) drow at false dot org
  606. Maxim Grigoriev (xtensa) maxim2405 at gmail dot com
  607. Andrew Cagney (acting head maintainer,
  608. release manager, global, MIPS, PPC, d10v,
  609. d30v, sim, mi, multi-arch, unwinder) cagney at gnu dot org
  610. Paul Hilfinger (Ada) hilfingr@eecs.berkeley.edu
  611. David O'Brien (FreeBSD, host & native) obrien@freebsd.org
  612. Jason Thorpe (NetBSD, host & native) thorpej@netbsd.org
  613. Gaius Mulley (Modula-2) gaius@glam.ac.uk
  614. Kei Sakamoto (m32r) sakamoto.kei@renesas.com
  615. Orjan Friberg (CRIS) orjanf@axis.com
  616. Qinwei (score-elf) qinwei@sunnorth.com.cn
  617. Randolph Chung (HPPA) tausq@debian.org
  618. Elena Zannoni (Global, event loop, generic
  619. symtabs, DWARF readers, ELF readers, stabs
  620. readers, readline) ezannoni@gmail.com
  621. Adam Fedor (Objective C) fedor@gnu.org
  622. Corinna Vinschen (xstormy16-elf) vinschen@redhat.com
  623. Theodore A. Roth (avr) troth@openavr.org
  624. Stephane Carrez (m68hc11-elf, tui) Stephane.Carrez@gmail.com
  625. Alfred M. Szmidt (GNU Hurd) ams@gnu.org
  626. Stan Shebs (Global) stanshebs@google.com
  627. Folks that have been caught up in a paper trail:
  628. David Carlton carlton@bactrian.org
  629. ;; Local Variables:
  630. ;; coding: utf-8
  631. ;; End: