From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Joshua Lock <josh@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/5] clutter_git: update to 1.8.2 tag
Date: Tue, 13 Dec 2011 21:20:04 +0000 [thread overview]
Message-ID: <5518182.4uSUpxrDi7@helios> (raw)
In-Reply-To: <4EE7B848.3070405@linux.intel.com>
On Tuesday 13 December 2011 12:40:40 Joshua Lock wrote:
> On 13/12/11 12:34, Khem Raj wrote:
> > On Tue, Dec 13, 2011 at 12:24 PM, Joshua Lock <josh@linux.intel.com>
wrote:
> >> -SRCREV = "39db46123ed6bbbc3e6ad359a64d4d344ca9e11b"
> >> -PV = "1.8.0+git${SRCPV}"
> >> +# the 1.8.2 tag
> >> +SRCREV = "9041ea42655dfc1422ce88eab931382dd400d13a"
> >> +PV = "1.8.2+git${SRCPV}"
> >
> > you could also use the tag name instead of SHA for SRCREV I think
>
> Indeed we can, however we've seen problems which I can't recall the
> details of in the past when doing so. Therefore I decided to avoid it
> this time.
It does work, it just forces a fetch on every parse which is not really
desirable. It's really no hardship to use the SHA1 especially if it's
accompanied by a comment with the corresponding tag.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-13 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 20:24 [PATCH 0/5] Clutter upgrades Joshua Lock
2011-12-13 20:24 ` [PATCH 1/5] cogl: upgrade to latest stable cogl 1.8.2 Joshua Lock
2011-12-13 20:24 ` [PATCH 2/5] clutter: upgrade to 1.8.2 Joshua Lock
2011-12-13 20:24 ` [PATCH 3/5] cogl: update git recipe " Joshua Lock
2011-12-13 20:24 ` [PATCH 4/5] clutter_git: update to 1.8.2 tag Joshua Lock
2011-12-13 20:34 ` Khem Raj
2011-12-13 20:40 ` Joshua Lock
2011-12-13 21:20 ` Paul Eggleton [this message]
2011-12-13 22:18 ` Saul Wold
2011-12-13 22:39 ` Khem Raj
2011-12-13 22:43 ` Paul Eggleton
2011-12-13 20:24 ` [PATCH 5/5] distro_tracking_fields: update cogl and clutter Joshua Lock
2011-12-15 18:36 ` [PATCH 0/5] Clutter upgrades Saul Wold
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=5518182.4uSUpxrDi7@helios \
--to=paul.eggleton@linux.intel.com \
--cc=josh@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.