From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Upgrade gcc 4.6.0 to latest on FSF 4.6 branch
Date: Tue, 14 Jun 2011 16:10:18 +0100 [thread overview]
Message-ID: <1308064218.25285.266.camel@phil-desktop> (raw)
In-Reply-To: <cover.1307937636.git.raj.khem@gmail.com>
On Sun, 2011-06-12 at 21:03 -0700, Khem Raj wrote:
> This patch brings in new patches from gcc 4.6 FSF branch
> And refreshes the headers of existing backported patches
> to not have git patch numbers in comments
>
> I am not sending the patch itself to mailing list due to its
> large size so please review it on the contrib tree itself
This patch doesn't seem to have bumped PR on gcc-4.6.0.bb even though
the SRC_URI has changed. Was that intentional?
p.
prev parent reply other threads:[~2011-06-14 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 4:03 [PATCH 0/1] Upgrade gcc 4.6.0 to latest on FSF 4.6 branch Khem Raj
2011-06-13 8:51 ` Phil Blundell
2011-06-13 9:01 ` Koen Kooi
2011-06-13 17:12 ` Khem Raj
2011-06-14 9:28 ` Phil Blundell
2011-06-14 9:43 ` Koen Kooi
2011-06-14 12:37 ` Richard Purdie
2011-06-15 2:33 ` Khem Raj
2011-06-14 15:10 ` Phil Blundell [this message]
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=1308064218.25285.266.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.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