From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, dvhart@linux.intel.com,
poky@yoctoproject.org, saul.wold@intel.com
Subject: [PATCH 0/1] kern-tools: fix meta-intel builds
Date: Tue, 8 May 2012 23:48:43 -0400 [thread overview]
Message-ID: <cover.1336535085.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
This fixes a problem reported by Tom and Darren when the latest tools
updates were used against meta intel. Some optional code that supported
merge meta and BSP branches wasn't handling the case where a BSP layer
might not be tracking the HEAD of the meta branch, and hence blowing up
its test to see if the meta branch needs to be thawed.
The fix was simple. Adjust the threshold for declaring the meta content
global.
cc: Tom Zanussi <tom.zanussi@intel.com>
cc: Darren Hart <dvhart@linux.intel.com>
Cheers,
Bruce
The following changes since commit 8afd5747802c4eb0e8296e440bd7366393595f8e:
Bruce Ashfield (1):
kernel-yocto: export GUILT_BASE
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kern-tools
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kern-tools
Bruce Ashfield (1):
kern-tools: checkpoint restoration for reset branches
.../kern-tools/kern-tools-native_git.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2012-05-09 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 3:48 Bruce Ashfield [this message]
2012-05-09 3:48 ` [PATCH 1/1] kern-tools: checkpoint restoration for reset branches Bruce Ashfield
2012-05-09 15:40 ` Darren Hart
2012-05-09 15:48 ` Bruce Ashfield
2012-05-09 16:02 ` Phil Blundell
2012-05-09 16:11 ` Bruce Ashfield
2012-05-09 16:42 ` Bruce Ashfield
2012-05-09 19:43 ` 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=cover.1336535085.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.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