# [PATCH] Documentation: remove warning that "git bisect skip" may slow bisection 3 messages from 2009-06-13 to 2009-06-13. Participants: Christian Couder, Stephen Boyd. Thread: https://gitlist.dev/t/19798 ## Christian Couder, 2009-06-13 05:22 Subject: [PATCH] Documentation: remove warning that "git bisect skip" may slow bisection Message-ID: <20090613052258.4209.23374.chriscool@tuxfamily.org> URL: https://gitlist.dev/e/20090613052258.4209.23374.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 --- 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 "''..''" notation. For example: -- 1.6.3.GIT ``` ## Stephen Boyd, 2009-06-13 08:14 Subject: Re: [PATCH] Documentation: remove warning that "git bisect skip" may slow bisection Message-ID: <4A335FEC.6060309@gmail.com> URL: https://gitlist.dev/e/4A335FEC.6060309%40gmail.com In-Reply-To: <20090613052258.4209.23374.chriscool@tuxfamily.org> ``` 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 "''..''" notation. For example: > Can this be "git may eventually be unable to tell" instead? ``` ## Christian Couder, 2009-06-13 11:13 Subject: Re: [PATCH] Documentation: remove warning that "git bisect skip" may slow bisection Message-ID: <200906131313.28411.chriscool@tuxfamily.org> URL: https://gitlist.dev/e/200906131313.28411.chriscool%40tuxfamily.org In-Reply-To: <4A335FEC.6060309@gmail.com> ``` 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 "''..''" 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. ```