Documentation: describe how to "bisect skip" a range of commits
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Christian Couder committed
Dec 2, 2008 at 14:53 UTC
5413812f0800e5530036671ee55476f2771ab828
2 files changed
+21
-2
Documentation/git-bisect.txt
+20
-1
@@ -19,7 +19,7 @@ on the subcommand:
19
git bisect start [<bad> [<good>...]] [--] [<paths>...]
20
git bisect bad [<rev>]
21
git bisect good [<rev>...]
22
- git bisect skip [<rev>...]
22
+ git bisect skip [(<rev>|<range>)...]
23
git bisect reset [<branch>]
24
git bisect visualize
25
git bisect replay <logfile>
@@ -164,6 +164,25 @@ But computing the commit to test may be slower afterwards and git may
164
eventually not be able to tell the first bad among a bad and one or
165
more "skip"ped commits.
166
167
+You can even skip a range of commits, instead of just one commit,
168
+using the "'<commit1>'..'<commit2>'" notation. For example:
169
+
170
+------------
171
+$ git bisect skip v2.5..v2.6
172
+------------
173
+
174
+would mean that no commit between `v2.5` excluded and `v2.6` included
175
+can be tested.
176
+
177
+Note that if you want to also skip the first commit of a range you can
178
+use something like:
179
+
180
+------------
181
+$ git bisect skip v2.5 v2.5..v2.6
182
+------------
183
+
184
+and the commit pointed to by `v2.5` will be skipped too.
185
+
186
Cutting down bisection by giving more parameters to bisect start
187
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
188
git-bisect.sh
+1
-1
@@ -9,7 +9,7 @@ git bisect bad [<rev>]
9
mark <rev> a known-bad revision.
10
git bisect good [<rev>...]
11
mark <rev>... known-good revisions.
12
-git bisect skip [<rev>...]
12
+git bisect skip [(<rev>|<range>)...]
13
mark <rev>... untestable revisions.
14
git bisect next
15
find next bisection to test and check it out.