From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: Step down from maintainerships
Date: Sun, 10 Oct 2004 22:15:00 -0000 [thread overview]
Message-ID: <vt2lleenrto.fsf@zenia.home> (raw)
After giving a lot of thought to how to get the most from limited
time, energy and ability, I've decided to step down from my GDB
maintainerships. I've volunteered as symtab maintainer for five
years, and it's time to give other folks a turn. I hope to continue
to contribute to GDB in other ways as I have since 1997.
There are a few outstanding patches that I had hoped to take care of
before stepping down, but then this last week some more came in, and I
realized I'd probably never get caught up. If they remain unreviewed
I'll try to comment on them as I'm able; naturally, my reviews won't
be binding.
2004-10-10 Jim Blandy <jimb@redhat.com>
* MAINTAINERS (generic symtabs, dwarf readers, elf reader, stabs
reader, tracing bytecode stuff): Remove self.
Index: gdb/MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.290
diff -c -p -r1.290 MAINTAINERS
*** gdb/MAINTAINERS 8 Oct 2004 01:35:48 -0000 1.290
--- gdb/MAINTAINERS 10 Oct 2004 21:55:11 -0000
*************** gdb/MAINTAINERS Elena Zannoni ezan
*** 217,238 ****
For the part of top.c related to the event loop,
send questions to ezannoni@redhat.com
! generic symtabs Jim Blandy jimb@redhat.com
! Elena Zannoni ezannoni@redhat.com
! dwarf readers Jim Blandy jimb@redhat.com
! Elena Zannoni ezannoni@redhat.com
! elf reader Jim Blandy jimb@redhat.com
! Elena Zannoni ezannoni@redhat.com
! stabs reader Jim Blandy jimb@redhat.com
! Elena Zannoni ezannoni@redhat.com
coff reader Philippe De Muyter phdm@macqel.be
xcoff reader Any maintainer can modify this; please send tricky
ones to Kevin Buettner <kevinb@redhat.com>
HP/UX readers Any [past] maintainer can modify this.
Please send tricky ones to the symtabs maintainers.
! tracing bytecode stuff Jim Blandy jimb@redhat.com
! (Global Maintainers)
tracing Michael Snyder msnyder@redhat.com
threads Michael Snyder msnyder@redhat.com
Mark Kettenis kettenis@gnu.org
--- 217,233 ----
For the part of top.c related to the event loop,
send questions to ezannoni@redhat.com
! generic symtabs Elena Zannoni ezannoni@redhat.com
! dwarf readers Elena Zannoni ezannoni@redhat.com
! elf reader Elena Zannoni ezannoni@redhat.com
! stabs reader Elena Zannoni ezannoni@redhat.com
coff reader Philippe De Muyter phdm@macqel.be
xcoff reader Any maintainer can modify this; please send tricky
ones to Kevin Buettner <kevinb@redhat.com>
HP/UX readers Any [past] maintainer can modify this.
Please send tricky ones to the symtabs maintainers.
! tracing bytecode stuff (Global Maintainers)
tracing Michael Snyder msnyder@redhat.com
threads Michael Snyder msnyder@redhat.com
Mark Kettenis kettenis@gnu.org
next reply other threads:[~2004-10-10 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:15 Jim Blandy [this message]
[not found] ` <16752 dot 3082 dot 255249 dot 837515 at localhost dot redhat dot com>
2004-10-15 17:51 ` Elena Zannoni
2004-10-17 19:59 ` Jim Blandy
2004-10-19 19:43 ` Jim Blandy
2004-10-19 22:14 ` [RFA] Don't apply line-number tweaks for non-GCC compilers Mark Kettenis
2004-10-19 22:15 ` Mark Kettenis
2004-11-09 13:16 ` Mark Kettenis
2004-11-09 19:54 ` Jim Blandy
2004-11-18 22:38 ` Mark Kettenis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vt2lleenrto.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox