From 5413812f0800e5530036671ee55476f2771ab828 Mon Sep 17 00:00:00 2001 From: Christian Couder Date: Tue, 2 Dec 2008 14:53:51 +0100 Subject: [PATCH] Documentation: describe how to "bisect skip" a range of commits Signed-off-by: Christian Couder --- Documentation/git-bisect.txt | 21 ++++++++++++++++++++- git-bisect.sh | 2 +- 2 files changed, 21 insertions(+), 2 deletions(-) diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt index 39034ec7d6..147ea38197 100644 --- a/Documentation/git-bisect.txt +++ b/Documentation/git-bisect.txt @@ -19,7 +19,7 @@ on the subcommand: git bisect start [ [...]] [--] [...] git bisect bad [] git bisect good [...] - git bisect skip [...] + git bisect skip [(|)...] git bisect reset [] git bisect visualize git bisect replay @@ -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 "''..''" 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/git-bisect.sh b/git-bisect.sh index ddbdba8af1..17a35f6adc 100755 --- a/git-bisect.sh +++ b/git-bisect.sh @@ -9,7 +9,7 @@ git bisect bad [] mark a known-bad revision. git bisect good [...] mark ... known-good revisions. -git bisect skip [...] +git bisect skip [(|)...] mark ... untestable revisions. git bisect next find next bisection to test and check it out. -- 2.11.4.GIT