Differences between version 17 and predecessor to the previous major change of KernelDevelopmentWithGit.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 17 | Last edited on Thursday, November 30, 2006 12:30:34 pm | by IanMcDonald | Revert |
| Older page: | version 16 | Last edited on Monday, November 27, 2006 2:44:57 pm | by IanMcDonald | Revert |
@@ -91,17 +91,28 @@
URL: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Pull: master:origin
</verbatim>
-!Using git-bisect
+!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>
+
+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.
+
+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:
<verbatim>
git-reset --hard COPY_HEAD
</verbatim>
where COPY_HEAD is your copy of HEAD....
However check the contents of the HEAD file as sometimes it's just a reference such as <tt>ref: refs/head/master</tt> in which case make a copy of that file which is being pointed to.
+
+In theory you can do this also by typing:
+<verbatim>
+git checkout master
+</verbatim>
!Working with branches
A key feature of git is to maintain branches of code. For example you might keep Linus' code and your own in separate branches.
