Skip to content

Commit 32d86ca

Browse files
chriscoolgitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent ebc9529 commit 32d86ca

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

Documentation/git-bisect.txt

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,9 +164,8 @@ to do it for you by issuing the command:
164164
$ git bisect skip # Current version cannot be tested
165165
------------
166166

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.
170169

171170
You can even skip a range of commits, instead of just one commit,
172171
using the "'<commit1>'..'<commit2>'" notation. For example:

0 commit comments

Comments
 (0)