From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] libcec: update libcec to latest version (1.8.2) as to include RasPi support
Date: Thu, 06 Sep 2012 09:30:05 +0100 [thread overview]
Message-ID: <1477981.pb89MerWOV@helios> (raw)
In-Reply-To: <50485B04.4030002@communistcode.co.uk>
On Thursday 06 September 2012 09:12:52 Jack Mitchell wrote:
> On 05/09/12 22:32, Paul Eggleton wrote:
> > On Wednesday 05 September 2012 21:28:18 Martin Jansa wrote:
> >> On Wed, Sep 05, 2012 at 03:16:10PM +0100, Paul Eggleton wrote:
> >>> It's not totally clear but it doesn't look like 1.8.2 has been released
> >>> yet judging from their website; if that's the case then PV should be set
> >>> to "1.8.1+git${SRCPV}".
> >>
> >> Or rather
> >> "1.8.1+gitr${SRCPV}"
> >> like most meta-* recipes
> >
> > This was discussed not that long ago IIRC - the r is superfluous for git.
> > In fact if you look at most OE-Core recipes that use SRCPV they do not
> > precede it with r.
> >
> > Cheers,
> > Paul
>
> So even though it is the 1.8.1 release commit it should still be tagged
> with the git SRCPV?
Well, I don't personally think so - if it really is 1.8.1 (and it's pointing
at the same revision as the "1.8.1" tag, so it ought to be) then I don't think
it should be needed.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-06 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 14:02 [PATCH 1/3] libplist: issues with parallel make so disable ml
2012-09-05 14:02 ` [PATCH 2/3] liblockdev: new recipe, new version of libcec requires it ml
2012-09-05 14:02 ` [PATCH 3/3] libcec: update libcec to latest version (1.8.2) as to include RasPi support ml
2012-09-05 14:16 ` Paul Eggleton
2012-09-05 19:28 ` Martin Jansa
2012-09-05 21:32 ` Paul Eggleton
2012-09-06 8:12 ` Jack Mitchell
2012-09-06 8:30 ` Paul Eggleton [this message]
2012-09-06 8:48 ` Jack Mitchell
2012-09-06 8:37 ` Andrei Gherzan
2012-09-06 8:47 ` Jack Mitchell
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=1477981.pb89MerWOV@helios \
--to=paul.eggleton@linux.intel.com \
--cc=ml@communistcode.co.uk \
--cc=openembedded-devel@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