git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David J. Mellor" <dmellor@whistlingcat.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, bfields@fieldses.org
Subject: [PATCH] Documentation: Remove spurious uses of "you" in git-bisect.txt.
Date: Wed, 25 Mar 2009 20:44:44 -0700	[thread overview]
Message-ID: <1238039084-4810-1-git-send-email-dmellor@whistlingcat.com> (raw)
In-Reply-To: <20090324220201.GM19389@fieldses.org>

These were added by accident in a42dea3.

This patch also rewords the description of how ranges of commits can be
skipped.

Signed-off-by: David J. Mellor <dmellor@whistlingcat.com>
---
 Documentation/git-bisect.txt |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index a356a2b..ffc02c7 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -151,7 +151,7 @@ $ git reset --hard HEAD~3		# try 3 revisions before what
 					# was suggested
 ------------
 
-Then you compile and test the chosen revision. Afterwards you mark
+Then compile and test the chosen revision, and afterwards mark
 the revision as good or bad in the usual manner.
 
 Bisect skip
@@ -175,8 +175,8 @@ using the "'<commit1>'..'<commit2>'" notation. For example:
 $ git bisect skip v2.5..v2.6
 ------------
 
-This tells the bisect process that no commit between `v2.5` excluded and
-`v2.6` included should be tested.
+This tells the bisect process that no commit after `v2.5`, up to and
+including `v2.6`, should be tested.
 
 Note that if you also want to skip the first commit of the range you
 would issue the command:
-- 
1.6.2.1

  reply	other threads:[~2009-03-26  3:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23  1:00 Minor documentation fixes David J. Mellor
2009-03-23  1:00 ` [PATCH 1/5] Documentation: removed some uses of the passive voice in git-bisect.txt David J. Mellor
2009-03-23  1:00   ` [PATCH 2/5] Documentation: minor grammatical fixes and rewording in git-bundle.txt David J. Mellor
2009-03-23  1:00     ` [PATCH 3/5] Documentation: minor grammatical fixes in git-cat-file.txt David J. Mellor
2009-03-23  1:00       ` [PATCH 4/5] Documentation: minor grammatical fixes in git-check-attr.txt David J. Mellor
2009-03-23  1:00         ` [PATCH 5/5] Documentation: minor grammatical fix in git-check-ref-format.txt David J. Mellor
2009-03-23  3:11   ` [PATCH 1/5] Documentation: removed some uses of the passive voice in git-bisect.txt David J. Mellor
2009-03-24 22:02     ` J. Bruce Fields
2009-03-26  3:44       ` David J. Mellor [this message]
2009-03-26  3:48         ` [PATCH] Documentation: Remove spurious uses of "you" " Junio C Hamano
2009-03-23  5:43   ` [PATCH 1/5] Documentation: removed some uses of the passive voice " 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=1238039084-4810-1-git-send-email-dmellor@whistlingcat.com \
    --to=dmellor@whistlingcat.com \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).