@matheusbsbs / matheus-bagliano / commits / c39ce91827
Fork 0

Bisect: add "bisect skip" to the documentation.

Also fix "bisect bad" and "bisect good" short usage description. Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Christian Couder committed Oct 22, 2007 at 07:49 UTC c39ce91827e6f8c9e2cbfb482f90fe6f58d4d573
1 file changed +17 -2
Documentation/git-bisect.txt
+17 -2
@@ -16,8 +16,9 @@ The command takes various subcommands, and different options depending
16 on the subcommand:
17
18 git bisect start [<bad> [<good>...]] [--] [<paths>...]
19 - git bisect bad <rev>
20 - git bisect good <rev>
19 + git bisect bad [<rev>]
20 + git bisect good [<rev>...]
21 + git bisect skip [<rev>...]
22 git bisect reset [<branch>]
23 git bisect visualize
24 git bisect replay <logfile>
@@ -134,6 +135,20 @@ $ git reset --hard HEAD~3 # try 3 revs before what
135 Then compile and test the one you chose to try. After that, tell
136 bisect what the result was as usual.
137
138 +Bisect skip
139 +~~~~~~~~~~~~
140 +
141 +Instead of choosing by yourself a nearby commit, you may just want git
142 +to do it for you using:
143 +
144 +------------
145 +$ git bisect skip # Current version cannot be tested
146 +------------
147 +
148 +But computing the commit to test may be slower afterwards and git may
149 +eventually not be able to tell the first bad among a bad and one or
150 +more "skip"ped commits.
151 +
152 Cutting down bisection by giving more parameters to bisect start
153 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
154