Documentation: remove warning saying that "git bisect skip" may slow bisection
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>
Christian Couder committed
Jun 13, 2009 at 13:11 UTC
32d86ca53195590f8d7df9f5f58683c9a924d5af
1 file changed
+2
-3
Documentation/git-bisect.txt
+2
-3
@@ -164,9 +164,8 @@ to do it for you by issuing the command:
164
$ git bisect skip # Current version cannot be tested
165
------------
166
167
-But computing the commit to test may be slower afterwards and git may
168
-eventually not be able to tell the first bad commit among a bad commit
169
-and one or more skipped commits.
167
+But git may eventually be unable to tell the first bad commit among
168
+a bad commit and one or more skipped commits.
169
170
You can even skip a range of commits, instead of just one commit,
171
using the "'<commit1>'..'<commit2>'" notation. For example: