git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Genz" <liebundartig@freenet.de>
To: git@vger.kernel.org
Cc: gitster@pobox.com, "René Genz" <liebundartig@freenet.de>
Subject: [PATCH] doc: git-pull.txt use US spelling, fix minor typo
Date: Sun, 23 Apr 2017 18:45:25 +0200	[thread overview]
Message-ID: <1492965925-29744-1-git-send-email-liebundartig@freenet.de> (raw)

---
Instead of using two command lines I could have replaced the comma with a semicolon.

I do not mind, if this patch is squashed into the other minor typo fixes of mine:
3c228f462d02e76956062b8d8572158cbcdbbc7b


 Documentation/git-pull.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index 4470e4b..942af8e 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -67,7 +67,7 @@ with uncommitted changes is discouraged: while possible, it leaves you
 in a state that may be hard to back out of in the case of a conflict.
 
 If any of the remote changes overlap with local uncommitted changes,
-the merge will be automatically cancelled and the work tree untouched.
+the merge will be automatically canceled and the work tree untouched.
 It is generally best to get any local changes in working order before
 pulling or stash them away with linkgit:git-stash[1].
 
@@ -210,7 +210,8 @@ EXAMPLES
   current branch:
 +
 ------------------------------------------------
-$ git pull, git pull origin
+$ git pull
+$ git pull origin
 ------------------------------------------------
 +
 Normally the branch merged in is the HEAD of the remote repository,
-- 
1.9.1


             reply	other threads:[~2017-04-23 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 16:45 René Genz [this message]
2017-04-24  2:55 ` [PATCH] doc: git-pull.txt use US spelling, fix minor typo 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=1492965925-29744-1-git-send-email-liebundartig@freenet.de \
    --to=liebundartig@freenet.de \
    --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).