[OE-core] Why to make branch info is mandatory for non-master commit with latest bitbake

[zhenhua.luo at freescale.com]

Hi Richard, 

> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf Of Richard Purdie
> Sent: Monday, December 23, 2013 6:43 PM
> 
> On Mon, 2013-12-23 at 06:41 +0000, zhenhua.luo at freescale.com wrote:
> > Previously the branch name doesn't need to be defined when a
> > non-master branch commit is referred in recipe, this has been changed
> > in latest bitbake.
> >
> > Is this an intentional change? May I know the reason of the change if
> it is intentional?
> 
> It was intentional and was triggered by this change:
> 
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=f19546e02d3318ee69fd
> 0c34e21aa97b74c987ec
> 
> which is a sanity test added to fix certain failure cases where a given
> revision wasn't on a specified branch.
> 
> The bug was nasty since the fetcher was hitting the network in cases it
> shouldn't have been when a branch wasn't specified.
[Luo Zhenhua-B19537] I see, can bitbake be enhanced to support tag as well? Sometimes a commit might be contained by a tag rather than branch, e.g. tag created for rebased git tree. 


Best Regards,

Zhenhua