From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 0/2] Change gcc 4.6 recipes to use svn in SRC_URI
Date: Wed, 22 Jun 2011 17:00:20 +0100 [thread overview]
Message-ID: <1308758420.20015.82.camel@rex> (raw)
In-Reply-To: <cover.1308706692.git.raj.khem@gmail.com>
On Tue, 2011-06-21 at 18:43 -0700, Khem Raj wrote:
> changes since V1
>
> Separate out non gcc changes to a different pull request
> Patches are not attached inline due to sheer size of them
> as they might choke patchwork. The are only on the branch
>
> The following changes since commit 78de64f58b98101f5be5778e9ecbdaae5ba32997:
>
> binutils_2.21.bb: Fix ld segfault exposed by eglibc 2.14 on x86_64 (2011-06-21 17:58:06 -0700)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib kraj/gcc-4.6
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/gcc-4.6
>
> Khem Raj (2):
> gcc-4.6: Switch to using svn SRC_URI for recipe
> tcmode-default.inc: use 4.6 for GCCVERSION and SDKGCCVERSION
I'm afraid I don't like having "gcc 4.6" being so publicly visible. Its
fine for the recipe names but the PV itself really needs to be something
like "4.6.2+svn".
I say this as a person who'd have to deal with people claiming we're
behind on gcc since we were on 4.6[.0] :/
Cheers,
Richard
next prev parent reply other threads:[~2011-06-22 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 1:43 [PATCH V2 0/2] Change gcc 4.6 recipes to use svn in SRC_URI Khem Raj
2011-06-22 16:00 ` Richard Purdie [this message]
2011-06-22 16:03 ` Khem Raj
2011-06-22 16:05 ` Phil Blundell
2011-06-22 18:57 ` Richard Purdie
2011-06-22 16:08 ` Koen Kooi
2011-06-23 8:40 ` Khem Raj
2011-06-23 10:50 ` Richard Purdie
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=1308758420.20015.82.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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