From: Paul Campbell <pcampbell@kemitix.net>
To: git <git@vger.kernel.org>
Cc: David Greene <greened@obbligato.org>,
Paul Cartwright <paul.cartwright@ziilabs.com>,
Paul Campbell <pcampbell@kemitix.net>
Subject: [PATCH 3/4] contrib/subtree: Fix typo (s/incldued/included/)
Date: Wed, 13 Mar 2013 22:32:42 +0000 [thread overview]
Message-ID: <1363213963-4065-4-git-send-email-pcampbell@kemitix.net> (raw)
In-Reply-To: <1363213963-4065-1-git-send-email-pcampbell@kemitix.net>
From: Paul Cartwright <paul.cartwright@ziilabs.com>
Signed-off-by: Paul Campbell <pcampbell@kemitix.net>
---
contrib/subtree/git-subtree.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/subtree/git-subtree.txt b/contrib/subtree/git-subtree.txt
index 97dd3c9..e1bfa61 100644
--- a/contrib/subtree/git-subtree.txt
+++ b/contrib/subtree/git-subtree.txt
@@ -275,7 +275,7 @@ git-extensions repository in ~/git-extensions/:
name
You can omit the --squash flag, but doing so will increase the number
-of commits that are incldued in your local repository.
+of commits that are included in your local repository.
We now have a ~/git-extensions/git-subtree directory containing code
from the master branch of git://github.com/apenwarr/git-subtree.git
--
1.8.2
next prev parent reply other threads:[~2013-03-13 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 22:32 [PATCH 0/4] contrib/subtree: general updates Paul Campbell
2013-03-13 22:32 ` [PATCH 1/4] contrib/subtree: Teach push to abort if split fails Paul Campbell
2013-03-13 22:32 ` [PATCH 2/4] contrib/subtree: Teach push to use --force option Paul Campbell
2013-03-13 22:32 ` Paul Campbell [this message]
2013-03-13 22:32 ` [PATCH 4/4] contrib/subtree: Replace invisible carriage return with a visible \r Paul Campbell
2013-03-13 22:36 ` Paul Campbell
2013-03-13 22:42 ` [PATCH] " Paul Campbell
2013-03-14 2:52 ` [PATCH 0/4] contrib/subtree: general updates Miles Bader
2013-03-14 3:30 ` Junio C Hamano
2013-03-24 0:16 ` Paul Campbell
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=1363213963-4065-4-git-send-email-pcampbell@kemitix.net \
--to=pcampbell@kemitix.net \
--cc=git@vger.kernel.org \
--cc=greened@obbligato.org \
--cc=paul.cartwright@ziilabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.