[bitbake-devel] [PATCH] bitbake: bb.fetch2.git: Fix _latest_revision function while using tags

Richard Purdie richard.purdie at linuxfoundation.org
Tue Jan 7 13:40:55 UTC 2014


On Tue, 2014-01-07 at 11:36 +0100, Olof Johansson wrote:
> On 14-01-05 02:53 +0100, Andrei Gherzan wrote:
> > When getting the revision we must take into consideration if the name we are
> > looking for is a tag and in that case we need the dereferenced commit ID in
> > order to check for it existance in a specific branch.
> > 
> > So first search for the reference^{} commit ID and only if that returns nothing
> > get the name as it is.
> 
> I think this is the same issue I've tried to solve in a patch i
> sent in December (subject: bb.fetch2.git: support resolving both
> tags and branches). I haven't heard anything about it yet though.

I put this off as I wanted to spend some time and see if we couldn't
come up with something simpler. Andrei's patch is simpler, the question
is whether it covers all the cases and whether we even need the fallback
code?

I've merged the nobranch code since its clear there are cases when that
is the right thing to do and its a seperate issue to this.

Cheers,

Richard






More information about the bitbake-devel mailing list