From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@linux-foundation.org>, jgarzik <jgarzik@pobox.com>
Subject: [PATCH] doc: what a patch series is
Date: Tue, 8 May 2007 13:59:22 -0700 [thread overview]
Message-ID: <20070508135922.a13a292d.randy.dunlap@oracle.com> (raw)
Andrew, Jeff: would you update tpp.txt and patch-format.html
respectively to clarify this? (I can send patches if you prefer that.)
From: Randy Dunlap <randy.dunlap@oracle.com>
It seems that we need to clarify that a patch series is a
series of related patches rather than "here are some of my
patches as multiple (numbered) emails."
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/SubmittingPatches | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- linux-2.6.21-git10.orig/Documentation/SubmittingPatches
+++ linux-2.6.21-git10/Documentation/SubmittingPatches
@@ -363,7 +363,8 @@ area or subsystem of the kernel is being
The "summary phrase" in the email's Subject should concisely
describe the patch which that email contains. The "summary
phrase" should not be a filename. Do not use the same "summary
-phrase" for every patch in a whole patch series.
+phrase" for every patch in a whole patch series (where a "patch
+series" is an ordered sequence of multiple, related patches).
Bear in mind that the "summary phrase" of your email becomes
a globally-unique identifier for that patch. It propagates
reply other threads:[~2007-05-08 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070508135922.a13a292d.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®