lkml.org 
[lkml]   [2008]   [May]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: GIT bisection range errors
Date
 > > $ git checkout -b rc v2.6.26-rc1
> > $ git bisect start
> > $ git bisect bad
> > $ git bisect good v2.6.25
> >
> > Yet, during this I'm finding myself at 2.6.25-rc6 and 2.6.25-rc8
> > as the last two results (both good...).

> I reported a similar thing at the beginning of April
> http://lkml.org/lkml/2008/4/2/390 - 2.6.25-rc1 bad, 2.6.24 good, git
> dropped me back at 2.6.24-rc4 (again, according to the top level
> Makefile).

This is normal and expected, due to the distributed nature of git and
the fact that git-bisect operates on the full topology of history and
not just a linear sequence of commits.

Imagine history like:

A---B---C---D
\ /
\ /
\ /
E---F

where B is good and D is bad. Now, when you bisect, there is no way to
know whether, say, E is good or bad and hence the bisect process may
present E as a tree to try.

Now, if B is the 2.6.25 release, then since E branched off before B, it
will have a Makefile that says 2.6.25-rcX. Which is exactly the
behavior you are seeing.

In short, everything looks fine and is behaving as expected.

- R.


\
 
 \ /
  Last update: 2008-05-09 01:35    [W:0.185 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site