diff options
| author | Christian Couder <chriscool@tuxfamily.org> | 2009-06-13 13:11:02 +0200 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2009-06-13 10:48:59 -0700 |
| commit | 32d86ca53195590f8d7df9f5f58683c9a924d5af (patch) | |
| tree | 2882ceaee27f0a2c19e5910f3695e398a519f6d2 /Documentation/git-bisect.txt | |
| parent | ebc9529f0358bdb10192fa27bc75f5d4e452ce90 (diff) | |
| download | git-32d86ca53195590f8d7df9f5f58683c9a924d5af.tar.gz | |
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>
Diffstat (limited to 'Documentation/git-bisect.txt')
| -rw-r--r-- | 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 ffc02c737c..63e7a42cb3 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: |