On 13-03-05 12:56 PM, Kamble, Nitin A wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, March 05, 2013 9:50 AM
To: Kamble, Nitin A
Cc: linux-yo...@yoctoproject.org
Subject: Re: v3.8 kernel recipes in meta-intel
On 13-03-05 12:35 PM, Ka
> Not exactly, I must not be understanding what you are describing.
> There's no way for the kern-tools to create a commit ID. They can only work
> with what's present in the tree.
>
> If you see the SRCREV to "foo", and validate_branches is telling you that
> "foo" isn't present in the tree at al
On 13-03-05 12:35 PM, Kamble, Nitin A wrote:
So the topic branch commit is present much deeper in the branch with
different commit-id.
May be merging of the emgd branch resulted it. Is it issue with the
emgd branch rebased to an undesired point?
It shouldn't be. That commit shouldn't be pres
> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Tuesday, March 05, 2013 9:50 AM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org
> Subject: Re: v3.8 kernel recipes in meta-intel
>
> On 13-03-05 12:35 PM, Kamble, Nitin A wrote:
> >>>
> >>>
> >
> > So the topic branch commit is present much deeper in the branch with
> different commit-id.
> > May be merging of the emgd branch resulted it. Is it issue with the
> > emgd branch rebased to an undesired point?
>
> It shouldn't be. That commit shouldn't be present in the repository at all
