From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Rob Landley <rob@landley.net>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: update git pull info in SubmittingPatches
Date: Mon, 15 Jul 2013 18:10:01 -0400 [thread overview]
Message-ID: <51E47339.10500@windriver.com> (raw)
In-Reply-To: <51E47051.7030608@zytor.com>
On 13-07-15 05:57 PM, H. Peter Anvin wrote:
> Something else to put in there: if someone absolutely feels the need to
> put cover text before the patch, it should be separated from the patch
> proper by a scissor line (---8<---) or there is no support for
> automating the patch.
Sounds reasonable; I'll add it to my mental to-do list for sections
to update in this file.
next prev parent reply other threads:[~2013-07-15 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 21:18 [PATCH] Documentation: update git pull info in SubmittingPatches Paul Gortmaker
2013-07-15 21:31 ` Randy Dunlap
2013-07-15 21:40 ` Paul Gortmaker
2013-07-15 21:49 ` Randy Dunlap
2013-07-15 21:57 ` H. Peter Anvin
2013-07-15 22:10 ` Paul Gortmaker [this message]
[not found] ` <1374338111.3719.21@driftwood>
2013-07-23 14:47 ` Paul Gortmaker
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=51E47339.10500@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
/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