# [PATCH v2] Documentation: remove warning saying that "git bisect skip" may slow bisection

1 messages from 2009-06-13 to 2009-06-13. Participants: Christian Couder.
Thread: https://gitlist.dev/t/19801

## Christian Couder, 2009-06-13 11:11

Subject: [PATCH v2] Documentation: remove warning saying that "git bisect skip" may slow bisection
Message-ID: <20090613111103.20232.76402.chriscool@tuxfamily.org>
URL: https://gitlist.dev/e/20090613111103.20232.76402.chriscool%40tuxfamily.org

```
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>
---
 Documentation/git-bisect.txt |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index ffc02c7..63e7a42 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -164,9 +164,8 @@ to do it for you by issuing the command:
 $ 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:
-- 
1.6.3.GIT

```
