From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix for bitbake freeze due to git fetch during parse
Date: Wed, 22 Jun 2011 17:36:07 +0100 [thread overview]
Message-ID: <1308760567.20015.86.camel@rex> (raw)
In-Reply-To: <cover.1308677220.git.paul.eggleton@linux.intel.com>
On Tue, 2011-06-21 at 18:29 +0100, Paul Eggleton wrote:
> Addresses [YOCTO #1186]. See patch for further details. (Sending against
> poky-contrib since OE git is currently experiencing issues.)
>
> The following changes since commit 2163461ec94528ecf046a04edc5db3d2dd3a6b8b:
>
> systemtap: remove non-core COMPATIBLE_MACHINES (2011-06-16 22:14:06 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib paule/fix-uboot-srcrev
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=paule/fix-uboot-srcrev
>
> Paul Eggleton (1):
> u-boot: set SRCREV to a git revision instead of a tag reference
>
> meta/recipes-bsp/uboot/u-boot_2011.03.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
I've merged Paul's updated version of this. Its a hard problem given
git's way of handling tags/branches etc. so its probably the best we can
do in the circumstances...
Cheers,
Richard
prev parent reply other threads:[~2011-06-22 16:40 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
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 [this message]
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=1308760567.20015.86.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