From: Richard Earnshaw <rearnsha@arm.com>
To: gdb-patches@sourceware.org, gdb@sourceware.org
Subject: Move myself to Authorized Committer
Date: Fri, 28 Jan 2011 16:57:00 -0000 [thread overview]
Message-ID: <1296232991.9738.71.camel@e102346-lin.cambridge.arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
As a long standing GDB contributor my involvement with GDB goes well
back beyond the start of the GDB MAINTAINERS file. When that file was
created I was relatively active on GDB and it made some sense for me to
be put down as a Responsible Maintainer for the ARM port. These days,
although I'm still heavily involved with GNU tools work, the time I have
available for contributing to GDB is significantly less.
Unfortunately, the fact that I'm down as a responsible maintainers means
that I am now, in effect, becoming a road-block to the growing number of
engineers who are trying to contribute to the ARM port of GDB. That's
not a desirable position to be in.
Consequently, after considering the various options and talking to some
of the global maintainers, I've decided that it would be best if I move
myself to being an Authorized Committer. This should free up at the
very least the ability for the global maintainers to make and approve
changes to the ARM-specific parts of GDB and hopefully in time we will
gain additional people who have a specific interest in the ARM port who
can help in its maintenance.
I will continue to help with reviewing of GDB patches that relate to ARM
as time permits, but it is essential that I don't become part of the
problem.
R.
[-- Attachment #2: patch --]
[-- Type: text/x-patch, Size: 929 bytes --]
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.444
retrieving revision 1.445
diff -p -r1.444 -r1.445
*** MAINTAINERS 15 Sep 2010 22:53:53 -0000 1.444
--- MAINTAINERS 28 Jan 2011 16:32:26 -0000 1.445
*************** the native maintainer when resolving ABI
*** 255,261 ****
alpha --target=alpha-elf ,-Werror
arm --target=arm-elf ,-Werror
- Richard Earnshaw rearnsha@arm.com
avr --target=avr ,-Werror
Tristan Gingold gingold@adacore.com
--- 255,260 ----
*************** under no obligation to review posted pat
*** 429,434 ****
--- 428,434 ----
to do so!
PowerPC Andrew Cagney cagney@gnu.org
+ ARM Richard Earnshaw rearnsha@arm.com
CRIS Hans-Peter Nilsson hp@axis.com
IA64 Jeff Johnston jjohnstn@redhat.com
MIPS Joel Brobecker brobecker@adacore.com
reply other threads:[~2011-01-28 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1296232991.9738.71.camel@e102346-lin.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).