From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org, poky@yoctoproject.org,
saul.wold@intel.com
Subject: Re: [PATCH 1/1] kern-tools: checkpoint restoration for reset branches
Date: Wed, 09 May 2012 08:40:31 -0700 [thread overview]
Message-ID: <4FAA8FEF.9050702@linux.intel.com> (raw)
In-Reply-To: <893d8018c655f70ada731eaf5f03b178f4dfe2b3.1336535085.git.bruce.ashfield@windriver.com>
On 05/08/2012 08:48 PM, Bruce Ashfield wrote:
> Updating the SRCREV to pickup the following fix:
>
> createme: fix checkpoint restoration for reset branches
>
> The meta branch can optionally be merged out to BSP branches. This removes
> the need to restore the checkpoint when working with the tree. The way
> it detects the merge is by checking to see how many branches contain the
> meta data. If there's more than one, the branch was was merged out.
>
> Unless you are a BSP that isn't tracking the latest meta, and you get
> meta and meta-orig created. That's two branches and the code opts to not
> restore the checkpoint, which leads to configuration errors.
>
> The fix is simple. We allow for 2 or less branches with meta, and will
> still restore the checkpoint. Three and up, we won't.
>
Uhm... am I the only one for whom this language is really confusing?
"merged out" ?
"restore the checkpoint" ?
Why does a BSP using a different meta SRCREV get two meta branches?
The fix of incrementing the allowed count of meta branches honestly
feels like a bandaid. Why do we create two in the first place?
Regardless, this is a blocker for working with meta-intel, so we need
this in. But it does seem to me that a more direct solution may be
needed. Bruce, can you help fill me in re. the above?
--
Darren
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> .../kern-tools/kern-tools-native_git.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> index b6fab39..b5e203e 100644
> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
>
> DEPENDS = "git-native guilt-native"
>
> -SRCREV = "9bb704df0a86578b8ae1f4c85e45089bef28e026"
> +SRCREV = "de3649840e8e3ca25bc79d2444f04a1b158a1769"
> PR = "r12"
> PV = "0.1+git${SRCPV}"
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-05-09 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 3:48 [PATCH 0/1] kern-tools: fix meta-intel builds Bruce Ashfield
2012-05-09 3:48 ` [PATCH 1/1] kern-tools: checkpoint restoration for reset branches Bruce Ashfield
2012-05-09 15:40 ` Darren Hart [this message]
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=4FAA8FEF.9050702@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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