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 19:57:40 +0100 [thread overview]
Message-ID: <1308769060.20015.97.camel@rex> (raw)
In-Reply-To: <1308758709.21613.104.camel@phil-desktop>
On Wed, 2011-06-22 at 17:05 +0100, Phil Blundell wrote:
> On Wed, 2011-06-22 at 17:00 +0100, Richard Purdie wrote:
> > 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".
>
> Well, er, gcc 4.6.1 hasn't even been released yet. I think "4.6.0
> +svn" (or just "4.6+svn") is the only reasonable thing to put there.
> Calling it 4.6.2 would definitely be misleading.
I'm just thinking ahead ;-)
Cheers,
Richard
next prev parent reply other threads:[~2011-06-22 19:01 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
2011-06-22 16:03 ` Khem Raj
2011-06-22 16:05 ` Phil Blundell
2011-06-22 18:57 ` Richard Purdie [this message]
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=1308769060.20015.97.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