threads / patch / 45583

patchgit-bisect.txt: add missing word

Subject: [PATCH] git-bisect.txt: add missing word

## tl;dr

2 messages between Apr 1, 2017 and Apr 1, 2017. Diffs are folded; open one to read it.

replies: 1people: 2as markdown or json

Quentin Pradet· Apr 1, 2017, 06:40 UTC · lore
Signed-off-by: Quentin Pradet <quentin.pradet@gmail.com>
---
 Documentation/git-bisect.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Show changes to Documentation/git-bisect.txt +3 −3
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· Apr 1, 2017, 18:34 UTC · re: Quentin Pradet · lore

Re: [PATCH] git-bisect.txt: add missing word

Quentin Pradet <quentin.pradet@gmail.com> writes:
> Signed-off-by: Quentin Pradet <quentin.pradet@gmail.com>
> ---
>  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.
Show 16 quoted lines
> 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.

← back to recent threads