rev-list documentation: add "--bisect-all".
Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Christian Couder committed
Oct 22, 2007 at 07:48 UTC
3ac9f612cbbb146743c0734c707e6cb512c43aa4
1 file changed
+16
Documentation/git-rev-list.txt
+16
@@ -34,6 +34,7 @@ SYNOPSIS
34
[ \--pretty | \--header ]
35
[ \--bisect ]
36
[ \--bisect-vars ]
37
+ [ \--bisect-all ]
38
[ \--merge ]
39
[ \--reverse ]
40
[ \--walk-reflogs ]
@@ -354,6 +355,21 @@ the expected number of commits to be tested if `bisect_rev`
355
turns out to be bad to `bisect_bad`, and the number of commits
356
we are bisecting right now to `bisect_all`.
357
358
+--bisect-all::
359
+
360
+This outputs all the commit objects between the included and excluded
361
+commits, ordered by their distance to the included and excluded
362
+commits. The farthest from them is displayed first. (This is the only
363
+one displayed by `--bisect`.)
364
+
365
+This is useful because it makes it easy to choose a good commit to
366
+test when you want to avoid to test some of them for some reason (they
367
+may not compile for example).
368
+
369
+This option can be used along with `--bisect-vars`, in this case,
370
+after all the sorted commit objects, there will be the same text as if
371
+`--bisect-vars` had been used alone.
372
+
373
--
374
375
Commit Ordering