path: root/Documentation/git-bisect.txt
diff options
authorChristian Couder <>2007-10-22 05:49:23 (GMT)
committerJunio C Hamano <>2007-10-27 06:27:24 (GMT)
commitc39ce91827e6f8c9e2cbfb482f90fe6f58d4d573 (patch)
treee580a5213835d501477236a60c5c93ff9c42de76 /Documentation/git-bisect.txt
parent155fc795b9c613af79781ebec5fd8eda084e1636 (diff)
Bisect: add "bisect skip" to the documentation.
Also fix "bisect bad" and "bisect good" short usage description. Signed-off-by: Christian Couder <> Signed-off-by: Shawn O. Pearce <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-bisect.txt')
1 files changed, 17 insertions, 2 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 1072fb8..785f381 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -16,8 +16,9 @@ The command takes various subcommands, and different options depending
on the subcommand:
git bisect start [<bad> [<good>...]] [--] [<paths>...]
- git bisect bad <rev>
- git bisect good <rev>
+ git bisect bad [<rev>]
+ git bisect good [<rev>...]
+ git bisect skip [<rev>...]
git bisect reset [<branch>]
git bisect visualize
git bisect replay <logfile>
@@ -134,6 +135,20 @@ $ git reset --hard HEAD~3 # try 3 revs before what
Then compile and test the one you chose to try. After that, tell
bisect what the result was as usual.
+Bisect skip
+Instead of choosing by yourself a nearby commit, you may just want git
+to do it for you using:
+$ git bisect skip # Current version cannot be tested
+But computing the commit to test may be slower afterwards and git may
+eventually not be able to tell the first bad among a bad and one or
+more "skip"ped commits.
Cutting down bisection by giving more parameters to bisect start