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

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

[Christian Couder]

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..5d015fc 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 not be able 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

Re: [PATCH] Documentation: remove warning that "git bisect skip" may slow bisection

[Stephen Boyd]

Christian Couder wrote:
> -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 not be able 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:
>   

Can this be "git may eventually be unable to tell" instead?

Re: [PATCH] Documentation: remove warning that "git bisect skip" may slow bisection

[Christian Couder]

Le Saturday 13 June 2009, Stephen Boyd a écrit :
> Christian Couder wrote:
> > -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 not be able 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:
>
> Can this be "git may eventually be unable to tell" instead?

Yes, I just sent a v2 with this change.

Thanks,
Christian.