diff options
authorChristian Couder <>2008-12-02 13:53:51 (GMT)
committerJunio C Hamano <>2008-12-02 23:29:12 (GMT)
commit5413812f0800e5530036671ee55476f2771ab828 (patch)
parent1a66a489d09e7b8629fa7e4184c78703f4eed335 (diff)
Documentation: describe how to "bisect skip" a range of commits
Signed-off-by: Christian Couder <>
2 files changed, 21 insertions, 2 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 39034ec..147ea38 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -19,7 +19,7 @@ on the subcommand:
git bisect start [<bad> [<good>...]] [--] [<paths>...]
git bisect bad [<rev>]
git bisect good [<rev>...]
- git bisect skip [<rev>...]
+ git bisect skip [(<rev>|<range>)...]
git bisect reset [<branch>]
git bisect visualize
git bisect replay <logfile>
@@ -164,6 +164,25 @@ 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.
+You can even skip a range of commits, instead of just one commit,
+using the "'<commit1>'..'<commit2>'" notation. For example:
+$ git bisect skip v2.5..v2.6
+would mean that no commit between `v2.5` excluded and `v2.6` included
+can be tested.
+Note that if you want to also skip the first commit of a range you can
+use something like:
+$ git bisect skip v2.5 v2.5..v2.6
+and the commit pointed to by `v2.5` will be skipped too.
Cutting down bisection by giving more parameters to bisect start
diff --git a/ b/
index ddbdba8..17a35f6 100755
--- a/
+++ b/
@@ -9,7 +9,7 @@ git bisect bad [<rev>]
mark <rev> a known-bad revision.
git bisect good [<rev>...]
mark <rev>... known-good revisions.
-git bisect skip [<rev>...]
+git bisect skip [(<rev>|<range>)...]
mark <rev>... untestable revisions.
git bisect next
find next bisection to test and check it out.