Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.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 22:43:52 +0000	[thread overview]
Message-ID: <8174007.kBAyhH3BGm@helios> (raw)
In-Reply-To: <20111213223928.GA15239@sakrah.homelinux.org>

On Tuesday 13 December 2011 14:39:28 Khem Raj wrote:
> is this some limitation of fetchers ?

Not really, it's just we need the actual SHA1 to construct ${PV} at parse 
time, and if the specified SRCREV is not a SHA1 the git fetcher has no way of 
knowing if it refers to a tag or a branch (which may also have changed since 
the last parse) until it can contact the repository, so it has to do that 
immediately.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-12-13 22:50 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
2011-12-13 22:18         ` Saul Wold
2011-12-13 22:39         ` Khem Raj
2011-12-13 22:43           ` Paul Eggleton [this message]
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=8174007.kBAyhH3BGm@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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