From: Elvis Dowson <elvis.dowson@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [v2] gcc-4.8: Refactor gcc-4.8.0 patch files.
Date: Thu, 4 Apr 2013 13:16:41 +0400 [thread overview]
Message-ID: <F81A0AC1-9DA1-4A74-949D-94FA709BFD43@gmail.com> (raw)
In-Reply-To: <B42120AF-E508-4363-8249-E94E10A2957D@gmail.com>
On Apr 4, 2013, at 11:41 AM, Khem Raj <raj.khem@gmail.com> wrote:
> I have staged this patch in http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-4.8
Thanks, Khem!
Could we do the same for the gcc-4.7 patches, as well, as those recipes are updated for 4.7.3 and newer, and subsequently retired to the meta-openembedded/toolchain layer?
Elvis Dowson
next prev parent reply other threads:[~2013-04-04 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 8:23 [v2] gcc-4.8: Refactor gcc-4.8.0 patch files Elvis Dowson
2013-04-04 7:41 ` Khem Raj
2013-04-04 9:16 ` Elvis Dowson [this message]
2013-04-04 14:55 ` Khem Raj
2013-05-17 17:32 ` Elvis Dowson
2013-05-17 19:05 ` [openembedded-core-contrib] " Khem Raj
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=F81A0AC1-9DA1-4A74-949D-94FA709BFD43@gmail.com \
--to=elvis.dowson@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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