On Sat, 3 Apr 2010 03:46:37 -0700 (PDT)
bugzilla-dae...@freedesktop.org wrote:
> $ git bisect start
> $ git bisect good
> $ git bisect bad f6c7b911653fb1508256c63518ef0bd15d68186e
> Some good revs are not ancestor of the bad rev.
> git bisect cannot work properly in this case.
> Maybe you mistake good and bad revs?
>
> ?????? WTF ??????? How can a commit that I already had last night be more
> recent (in the sense of when I added it into my local tree - which is the only
> measure that matters) than one I only picked up a few minutes ago this
> morning?
>
> So **NO**, I am not going to use "git friggin' bisect" for you!
Bisect is specifically made to track down regressions - i.e. something used to
work but doesn't anymore. It should only start from somewhere the problem
exists.
It sounds to me like the tree you had was something like:
A---B---C or A---B---D---C
\--D
Where C had fixed a problem and D had not. In this case, bisecting from C makes
no sense, unless you want to do it backwards to find when the issue was
*fixed*. "bad" and "good" should probably have been called "present" and
"later", or some such.
If a particular revision doesn't build at all (exhibits some other problem than
that which you're trying to track down), I guess that's when to use the skip
command.
Basically it does a binary search down the revision history, although it might
split along merge/branch paths. bad means after the point you look for, good
means before, and the weighted words may be misleading.
Sorry you're having trouble and I hope this is more explanatory than annoying.
This was meant to describe my understanding of the tool.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
