diff options
author | Junio C Hamano <junio@hera.kernel.org> | 2008-12-03 03:51:10 +0000 |
---|---|---|
committer | Junio C Hamano <junio@hera.kernel.org> | 2008-12-03 03:51:10 +0000 |
commit | d796cea413d764b14d2f56ee9ba80216f8132424 (patch) | |
tree | 0f364ec687e9a14cb7a1837ea8036766649135a2 /git-bisect.txt | |
parent | f95312bcd463500c613bdb8073042145e26f9a94 (diff) | |
download | git-htmldocs-d796cea413d764b14d2f56ee9ba80216f8132424.tar.gz |
Autogenerated HTML docs for v1.6.1-rc1-23-g757c
Diffstat (limited to 'git-bisect.txt')
-rw-r--r-- | git-bisect.txt | 21 |
1 files changed, 20 insertions, 1 deletions
diff --git a/git-bisect.txt b/git-bisect.txt index 39034ec7d..147ea3819 100644 --- a/git-bisect.txt +++ b/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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |