mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: bisect: "start" accepts one bad and many good commits

Browse Source 
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
Christian Couder
2007-04-05 05:33:53 +02:00
committed by Junio C Hamano
parent 38a47fd6e3
commit 6fe9c570cc
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
Documentation/git-bisect.txt
View File

@ -15,7 +15,7 @@ DESCRIPTION
The command takes various subcommands, and different options depending The command takes various subcommands, and different options depending
on the subcommand: on the subcommand:
git bisect start [<paths>...] git bisect start [<bad> [<good>...]] [--] [<paths>...]
git bisect bad <rev> git bisect bad <rev>
git bisect good <rev> git bisect good <rev>
git bisect reset [<branch>] git bisect reset [<branch>]
@ -134,15 +134,26 @@ $ git reset --hard HEAD~3 # try 3 revs before what
Then compile and test the one you chose to try. After that, tell Then compile and test the one you chose to try. After that, tell
bisect what the result was as usual. bisect what the result was as usual.
Cutting down bisection by giving path parameter to bisect start Cutting down bisection by giving more parameters to bisect start
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can further cut down the number of trials if you know what part of You can further cut down the number of trials if you know what part of
the tree is involved in the problem you are tracking down, by giving the tree is involved in the problem you are tracking down, by giving
paths parameters when you say `bisect start`, like this: paths parameters when you say `bisect start`, like this:
------------ ------------
$ git bisect start arch/i386 include/asm-i386 $ git bisect start -- arch/i386 include/asm-i386
------------
If you know beforehand more than one good commits, you can narrow the
bisect space down without doing the whole tree checkout every time you
give good commits. You give the bad revision immediately after `start`
and then you give all the good revisions you have:
------------
$ git bisect start v2.6.20-rc6 v2.6.20-rc4 v2.6.20-rc1 --
# v2.6.20-rc6 is bad
# v2.6.20-rc4 and v2.6.20-rc1 are good
------------ ------------
Bisect run Bisect run