lkml.org 
[lkml]   [2008]   [May]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: GIT bisection range errors
On 09-05-08 01:33, Roland Dreier wrote:

> 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.

Great explanation. Thanks.

Rene


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