From: cgd@google.com (Chris Demetriou)
To: gdb-patches@sourceware.org
Cc: cgd@google.com
Subject: [applied patch] Add myself to write-after-approval list
Date: Sun, 20 Jul 2008 21:59:00 -0000 [thread overview]
Message-ID: <20080720215849.F02A3306D3@localhost> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
I got write-after-approval access a few months ago, got busy, and
never added myself to the write-after-approval list.
So, I finally got around to it. Committed as obvious.
thanks,
chris
--
[gdb/ChangeLog]
2008-07-20 Chris Demetriou <cgd@google.com>
* MAINTAINERS (Write After Approval): Add self.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.397
diff -u -u -r1.397 MAINTAINERS
--- MAINTAINERS 15 Jul 2008 09:46:49 -0000 1.397
+++ MAINTAINERS 20 Jul 2008 21:55:43 -0000
@@ -475,6 +475,7 @@
Brendan Conoboy blc@redhat.com
Ludovic Courtès ludo@gnu.org
DJ Delorie dj@redhat.com
+Chris Demetriou cgd@google.com
Philippe De Muyter phdm@macqel.be
Dhananjay Deshpande dhananjayd@kpitcummins.com
Markus Deuling deuling@de.ibm.com
reply other threads:[~2008-07-20 21:59 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=20080720215849.F02A3306D3@localhost \
--to=cgd@google.com \
--cc=gdb-patches@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