Differences between version 18 and predecessor to the previous major change of KernelDevelopmentWithGit.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 18 | Last edited on Thursday, November 30, 2006 12:35:02 pm | by IanMcDonald | Revert |
| Older page: | version 17 | Last edited on Thursday, November 30, 2006 12:30:34 pm | by IanMcDonald | Revert |
@@ -93,11 +93,11 @@
</verbatim>
!Using git bisect
-To use git bisect go to the bad code first (normally where you are at) and then type <verbatim
>git bisect start</verbatim
> and then <verbatim
>git bisect bad</verbatim
>
+To use git bisect go to the bad code first (normally where you are at) and then type <tt
>git bisect start</tt
> and then <tt
>git bisect bad</tt
>
-Now go to a place that is good by checking out code something like <verbatim
>git-reset --hard v2.6.19-rc6</verbatim
>. If that proves to be good then do <verbatim
>git bisect good</verbatim
> and then do each change marking good or bad with <verbatim
>git bisect good</verbatim
> or <verbatim
>git bisect bad</verbatim
> until you find the problem.
+Now go to a place that is good by checking out code something like <tt
>git-reset --hard v2.6.19-rc6</tt
>. If that proves to be good then do <tt
>git bisect good</tt
> and then do each change marking good or bad with <tt
>git bisect good</tt
> or <tt
>git bisect bad</tt
> until you find the problem.
See also http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
Tip: Sometimes you lose track of where you came from so before you use git-bisect go into the .git directory and make a copy of the HEAD file so you know where you started! You can then always go back by typing:
