git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Quentin Pradet <quentin.pradet@gmail.com>
To: git@vger.kernel.org
Cc: Quentin Pradet <quentin.pradet@gmail.com>,
	Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>
Subject: [PATCH] git-bisect.txt: add missing word
Date: Sat,  1 Apr 2017 10:40:56 +0400	[thread overview]
Message-ID: <20170401064056.56969-1-quentin.pradet@gmail.com> (raw)

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


             reply	other threads:[~2017-04-01  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  6:40 Quentin Pradet [this message]
2017-04-01 18:34 ` [PATCH] git-bisect.txt: add missing word Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170401064056.56969-1-quentin.pradet@gmail.com \
    --to=quentin.pradet@gmail.com \
    --cc=antoine.delaite@ensimag.grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).