* [PATCH] git-bisect.txt: add missing word
@ 2017-04-01 6:40 Quentin Pradet
2017-04-01 18:34 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: Quentin Pradet @ 2017-04-01 6:40 UTC (permalink / raw)
To: git; +Cc: Quentin Pradet, Antoine Delaite
Signed-off-by: Quentin Pradet <quentin.pradet@gmail.com>
---
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] git-bisect.txt: add missing word
2017-04-01 6:40 [PATCH] git-bisect.txt: add missing word Quentin Pradet
@ 2017-04-01 18:34 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2017-04-01 18:34 UTC (permalink / raw)
To: Quentin Pradet; +Cc: git, Antoine Delaite
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.
> 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-04-01 18:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-01 6:40 [PATCH] git-bisect.txt: add missing word Quentin Pradet
2017-04-01 18:34 ` Junio C Hamano
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).