From: Matthew Gretton-Dann <matthew.gretton-dann@linaro.org>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: [linaro/gcc-4_8-branch] Backports from trunk and merge from gcc-4_8-branch.
Date: Tue, 14 May 2013 10:00:00 -0000 [thread overview]
Message-ID: <51920B37.8000409@linaro.org> (raw)
All,
I have just backported the following revisions from trunk to
linaro/gcc-4_8-branch: 197838, 198191, 198490-198496, 198575-198575, and 198677.
I have also merged the gcc-4_8-branch into linaro/gcc-4_8-branch up to
revision 198615.
Thanks,
Matt
--
Matthew Gretton-Dann
Toolchain Working Group, Linaro
next reply other threads:[~2013-05-14 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 10:00 Matthew Gretton-Dann [this message]
2013-06-06 8:28 Christophe Lyon
2013-08-14 15:50 Christophe Lyon
2013-09-11 15:25 Christophe Lyon
2013-10-17 22:08 Christophe Lyon
2013-12-09 15:09 Christophe Lyon
2013-12-20 21:21 Christophe Lyon
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=51920B37.8000409@linaro.org \
--to=matthew.gretton-dann@linaro.org \
--cc=Marcus.Shawcroft@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).