public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Jeremy Higdon <jeremy@sgi.com>
Subject: Re: [DOC] Linux kernel patch submission format
Date: Tue, 31 Aug 2004 17:37:41 +0100	[thread overview]
Message-ID: <1093970261.6200.45.camel@localhost.localdomain> (raw)
In-Reply-To: <413431F5.9000704@pobox.com>

On Tue, 2004-08-31 at 04:08 -0400, Jeff Garzik wrote:
> I tried to keep it as short as possible:  here is a page describing the 
> most optimal format for sending patches to Linux kernel developers.
> 
> 	http://linux.yyz.us/patch-format.html

--- patch-format.html.orig
+++ patch-format.html
@@ -83,6 +83,15 @@
 for the 5th time, resist the urge to attach 20 patches to a single
 email.
 
+</li><li><h2>One thread per set of patches</h2>
+
+The corollary to the above rule: when sending more than one patch in
+separate emails, make sure they stay together. Send the second and
+subsequent mails as <em>replies</em> to the first mail, rather than
+having each one start its own thread. (You should also ensure that
+your mail client obeys RFC2822 by including correct
+<TT>References:</TT> headers in replies.)
+
 </li><li><h2>Sign your work</h2>
 
 The sign-off is a simple line at the end of the explanation for the

-- 
dwmw2


  parent reply	other threads:[~2004-08-31 16:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  8:08 [DOC] Linux kernel patch submission format Jeff Garzik
2004-08-31 11:41 ` Neil Horman
2004-08-31 16:17 ` Erik Mouw
2004-08-31 16:37 ` David Woodhouse [this message]
2004-08-31 17:15   ` Jeff Garzik
2004-08-31 17:17     ` David Woodhouse
2004-08-31 17:25       ` Jeff Garzik
2004-09-01  1:27       ` Lee Revell
2004-09-22 18:59     ` Timothy Miller
2004-09-22 19:47       ` Horst von Brand
2004-09-23  7:46         ` Paul Jackson
2004-09-24 15:04         ` Timothy Miller
2004-09-24 15:22           ` Randy.Dunlap
2004-10-20 19:34             ` Timothy Miller
2004-08-31 17:07 ` Sam Ravnborg
2004-08-31 17:11   ` Jeff Garzik
2004-08-31 17:50 ` Patrick Dreker
2004-08-31 18:01   ` Jeff Garzik

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=1093970261.6200.45.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=akpm@osdl.org \
    --cc=jeremy@sgi.com \
    --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