From: Alan Hayward <alan.hayward@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [COMMITTED] Add myself to MAINTAINERS (Write After Approval)
Date: Fri, 23 Oct 2015 09:07:00 -0000 [thread overview]
Message-ID: <D24FB744.9189%alan.hayward@arm.com> (raw)
Hi All,
I've just added myself to Write After Approval maintainers.
Committed r229216
Cheers,
Alan.
Index: ChangeLog
===================================================================
--- ChangeLog (revision 229215)
+++ ChangeLog (revision 229216)
@@ -1,3 +1,7 @@
+2015-10-23 Alan Hayward <alan.hayward@arm.com>
+
+ * MAINTAINERS (Write After Approval): Add myself.
+
2015-10-20 H.J. Lu <hongjiu.lu@intel.com>
Sync with binutils-gdb:
Index: MAINTAINERS
===================================================================
--- MAINTAINERS (revision 229215)
+++ MAINTAINERS (revision 229216)
@@ -419,6 +419,7 @@
Stuart Hastings <stuart@apple.com>
Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
Pat Haugen <pthaugen@us.ibm.com>
+Alan Hayward <alan.hayward@arm.com>
Mark Heffernan <meheff@google.com>
George Helffrich <george@gcc.gnu.org>
Daniel Hellstrom <daniel@gaisler.com>
next reply other threads:[~2015-10-23 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 9:07 Alan Hayward [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-18 12:46 [COMMITTED] Add myself to MAINTAINERS (write after approval) Boris Kolpackov
2016-12-26 15:15 [COMMITTED] Add myself to MAINTAINERS (Write After Approval) Alexander Ivchenko
2016-11-18 16:37 Toma Tabacu
2015-12-18 5:23 Saraswati, Sujoy (OSTL)
2015-12-17 16:48 Andris Pavenis
2015-12-15 13:07 Alessandro Fanfarillo
2015-12-15 13:09 ` Jakub Jelinek
2015-12-15 16:13 ` Alessandro Fanfarillo
2015-10-09 11:50 Martin Liška
2015-10-09 10:56 Alexander Fomin
2015-10-09 11:26 ` Marek Polacek
2014-08-19 15:19 VandeVondele Joost
2014-08-19 0:53 Patrick Palka
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=D24FB744.9189%alan.hayward@arm.com \
--to=alan.hayward@arm.com \
--cc=gcc-patches@gcc.gnu.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).