# [PATCH] git-bisect.txt: add missing word 2 messages from 2017-04-01 to 2017-04-01. Participants: Quentin Pradet, Junio C Hamano. Thread: https://gitlist.dev/t/45583 ## Quentin Pradet, 2017-04-01 06:40 Subject: [PATCH] git-bisect.txt: add missing word Message-ID: <20170401064056.56969-1-quentin.pradet@gmail.com> URL: https://gitlist.dev/e/20170401064056.56969-1-quentin.pradet%40gmail.com ``` Signed-off-by: Quentin Pradet --- Documentation/git-bisect.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt index bdd915a66..90148bb07 100644 --- a/Documentation/git-bisect.txt +++ b/Documentation/git-bisect.txt @@ -137,9 +137,9 @@ respectively, in place of "good" and "bad". (But note that you cannot mix "good" and "bad" with "old" and "new" in a single session.) In this more general usage, you provide `git bisect` with a "new" -commit has some property and an "old" commit that doesn't have that -property. Each time `git bisect` checks out a commit, you test if that -commit has the property. If it does, mark the commit as "new"; +commit that has some property and an "old" commit that doesn't have +that property. Each time `git bisect` checks out a commit, you test if +that commit has the property. If it does, mark the commit as "new"; otherwise, mark it as "old". When the bisection is done, `git bisect` will report which commit introduced the property. -- 2.11.0 ``` ## Junio C Hamano, 2017-04-01 18:34 Subject: Re: [PATCH] git-bisect.txt: add missing word Message-ID: URL: https://gitlist.dev/e/xmqq37dsugcy.fsf%40gitster.mtv.corp.google.com In-Reply-To: <20170401064056.56969-1-quentin.pradet@gmail.com> ``` Quentin Pradet writes: > Signed-off-by: Quentin Pradet > --- > Documentation/git-bisect.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) The updated text is more grammatically correct. It would have been better if you avoided wrapping the lines unnecessarily, though. Thanks. > diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt > index bdd915a66..90148bb07 100644 > --- a/Documentation/git-bisect.txt > +++ b/Documentation/git-bisect.txt > @@ -137,9 +137,9 @@ respectively, in place of "good" and "bad". (But note that you cannot > mix "good" and "bad" with "old" and "new" in a single session.) > > In this more general usage, you provide `git bisect` with a "new" > -commit has some property and an "old" commit that doesn't have that > -property. Each time `git bisect` checks out a commit, you test if that > -commit has the property. If it does, mark the commit as "new"; > +commit that has some property and an "old" commit that doesn't have > +that property. Each time `git bisect` checks out a commit, you test if > +that commit has the property. If it does, mark the commit as "new"; > otherwise, mark it as "old". When the bisection is done, `git bisect` > will report which commit introduced the property. ```