lkml.org 
[lkml]   [2008]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Bisecting tip/auto-x86-next?
Date
On Thu, 19 Jun 2008 21:40:59 -0300, Kevin Winchester wrote:

> I am trying to track down a problem I reported here:
>
> http://lkml.org/lkml/2008/6/11/431
>
[...]
>
> that ruin the process? Can I manually choose a bisection point right
> after this warning was fixed? Is it likely that the fix for this

You certainly can move the bisection point. If you look at man git-bisect
it will mention the following:

"Avoiding to test a commit
If in a middle of bisect session, you know what the bisect suggested to
try next is not a good one to test (e.g. the change the commit
introduces is known not to work in your environment and you know it
does not have anything to do with the bug you are chasing), you may
want to find a near-by commit and try that instead.

It goes something like this:

$ git bisect good/bad # previous round was good/bad.
Bisecting: 337 revisions left to test after this
$ git bisect visualize # oops, that is uninteresting.
$ git reset --hard HEAD~3 # try 3 revs before what
# was suggested

Then compile and test the one you chose to try. After that, tell bisect
what the result was as usual."

It can be helpful to use gitk on the point that git bisect chooses/git
bisect visualise to see a graphical view of what's around it and then use
git reset <commitrev> to move yourself to a particular commit. You can
still use git bisect good/bad when you have moved to a particular commit
so long as the bisection processes has started.

--
Sitsofe | http://sucs.org/~sits/


\
 
 \ /
  Last update: 2008-06-20 09:19    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site