From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 1/1] u-boot: set SRCREV to a git revision instead of a tag reference
Date: Tue, 21 Jun 2011 18:42:09 +0100 [thread overview]
Message-ID: <201106211842.09743.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <D1BE4C62-7336-430E-9072-F827A2513CAD@dominion.thruhere.net>
On Tuesday 21 June 2011 18:34:54 Koen Kooi wrote:
> Can you add a comment above the rev in the lines of "bitbake sucks, we need
> to use a rev instead of a tag, this one maps to 2011.03"?
I will add a comment about the revision corresponding to the tag, good idea.
However, if you do specify a tag for SRCREV and SRCPV is part of PV, then
bitbake needs to fetch the revision from the repo in order to determine SRCPV
so it can expand PV when it comes to figure out if a recipe needs to be rebuilt
or not (remembering that if SRCREV isn't a full revision, bitbake can't tell
if what you've specified is a "fixed" tag or a potentially moving branch.
If you've got a better idea on how to handle this I'd love to hear it.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-21 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 17:29 [PATCH 0/1] Fix for bitbake freeze due to git fetch during parse Paul Eggleton
2011-06-21 17:29 ` [PATCH 1/1] u-boot: set SRCREV to a git revision instead of a tag reference Paul Eggleton
2011-06-21 17:33 ` Joshua Lock
2011-06-21 17:49 ` Paul Eggleton
2011-06-21 17:34 ` Koen Kooi
2011-06-21 17:42 ` Paul Eggleton [this message]
2011-06-21 17:54 ` Koen Kooi
2011-06-21 17:59 ` Paul Eggleton
2011-06-21 18:06 ` Tom Rini
2011-06-21 17:33 ` [PATCH 0/1] Fix for bitbake freeze due to git fetch during parse Koen Kooi
2011-06-22 16:36 ` 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=201106211842.09743.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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