From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Why to make branch info is mandatory for non-master commit with latest bitbake
Date: Mon, 23 Dec 2013 10:42:47 +0000 [thread overview]
Message-ID: <1387795367.11527.1.camel@ted> (raw)
In-Reply-To: <090257310d9e463d93ee5cd5fd4d27fe@DM2PR03MB399.namprd03.prod.outlook.com>
On Mon, 2013-12-23 at 06:41 +0000, zhenhua.luo@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=f19546e02d3318ee69fd0c34e21aa97b74c987ec
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.
Cheers,
Richard
next prev parent reply other threads:[~2013-12-23 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 6:41 Why to make branch info is mandatory for non-master commit with latest bitbake zhenhua.luo
2013-12-23 10:42 ` Richard Purdie [this message]
2013-12-24 6:25 ` zhenhua.luo
2014-03-14 11:50 ` Detlev Zundel
2014-03-16 22:58 ` Richard Purdie
[not found] ` <m27g7tqeoi.fsf@lamuella.denx.de>
2014-03-17 11:12 ` 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=1387795367.11527.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=zhenhua.luo@freescale.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