summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: ebc9529)
raw | patch | inline | side by side (parent: ebc9529)
author | Christian Couder <chriscool@tuxfamily.org> | |
Sat, 13 Jun 2009 11:11:02 +0000 (13:11 +0200) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sat, 13 Jun 2009 17:48:59 +0000 (10:48 -0700) |
This warning was probably useless anyway, but it is even more so now
that filtering of skipped commits is done in C and that there is a
mechanism to skip away from broken commits.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
that filtering of skipped commits is done in C and that there is a
mechanism to skip away from broken commits.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-bisect.txt | patch | blob | history |
index ffc02c737cf0a8d2bdb3cd812e0a23d43ee27fd7..63e7a42cb353e2cd0c8bbb6e83927bd1863a32cb 100644 (file)
$ git bisect skip # Current version cannot be tested
------------
-But computing the commit to test may be slower afterwards and git may
-eventually not be able to tell the first bad commit among a bad commit
-and one or more skipped commits.
+But git may eventually be unable to tell the first bad commit among
+a bad commit and one or more skipped commits.
You can even skip a range of commits, instead of just one commit,
using the "'<commit1>'..'<commit2>'" notation. For example: