From: Chris Packham <judge.packham@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Chris Packham <judge.packham@gmail.com>
Subject: [PATCH] fixup! Documentation/git-am: Document supported --patch-format options
Date: Mon, 17 Mar 2014 20:50:49 +1300 [thread overview]
Message-ID: <1395042649-16040-1-git-send-email-judge.packham@gmail.com> (raw)
In-Reply-To: <5326A5DB.5070407@gmail.com>
---
On 17/03/14 20:35, Chris Packham wrote:> On 17/03/14 19:39, Junio C Hamano wrote:
>> Chris Packham <judge.packham@gmail.com> writes:
>>
>>> Ping?
>>
>> Hasn't it been already cooking in 'next' for a few days?
>>
>
> Indeed I think I missed a "What's cooking". Do you want me to submit a
> fixup for the spelling mistake?
>
May as well just send it.
Documentation/git-am.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-am.txt b/Documentation/git-am.txt
index 76bd359..f8a7d0c 100644
--- a/Documentation/git-am.txt
+++ b/Documentation/git-am.txt
@@ -101,7 +101,7 @@ default. You can use `--no-utf8` to override this.
By default the command will try to detect the patch format
automatically. This option allows the user to bypass the automatic
detection and specify the patch format that the patch(es) should be
- intepreted as. Valid formats are mbox, stgit, stgit-series and hg.
+ interpreted as. Valid formats are mbox, stgit, stgit-series and hg.
-i::
--interactive::
--
1.7.9.5
prev parent reply other threads:[~2014-03-17 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 3:51 [PATCH] Documentation/git-am: Document supported --patch-format options Chris Packham
2014-03-16 7:59 ` Chris Packham
2014-03-17 6:39 ` Junio C Hamano
2014-03-17 7:35 ` Chris Packham
2014-03-17 7:50 ` Chris Packham [this message]
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=1395042649-16040-1-git-send-email-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--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).