From: "David Sherwood" <david.sherwood@arm.com>
To: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: [PATCH COMMITTED] MAINTAINERS (Write After Approval): Add myself.
Date: Fri, 28 Aug 2015 10:15:00 -0000 [thread overview]
Message-ID: <000001d0e17a$23185000$6948f000$@arm.com> (raw)
FYI.
ChangeLog:
2015-08-28 David Sherwood <david.sherwood@arm.com>
* MAINTAINERS: Add myself.
next reply other threads:[~2015-08-28 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 10:15 David Sherwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 15:30 Claudiu Zissulescu
2015-10-02 9:37 Louis Krupp
2015-08-27 20:19 Patrick Marlier
2015-07-29 17:48 Ville Voutilainen
2015-07-29 19:19 ` Marek Polacek
2015-07-29 19:50 ` Ville Voutilainen
2015-07-29 20:04 ` Ville Voutilainen
2015-07-29 20:08 ` Marek Polacek
2015-06-23 9:09 Ludovic Courtès
2013-08-30 19:44 [PATCH, committed] " Bernd Edlinger
2013-08-12 23:32 Adam Butcher
2006-12-15 21:19 [PATCH] [Committed] " Simon Martin
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='000001d0e17a$23185000$6948f000$@arm.com' \
--to=david.sherwood@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).