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 18:17:12 +0100 [thread overview]
Message-ID: <1093972632.6200.50.camel@localhost.localdomain> (raw)
In-Reply-To: <4134B221.9070203@pobox.com>
On Tue, 2004-08-31 at 13:15 -0400, Jeff Garzik wrote:
> hmmmm. While I do agree with the content, I'm trying to avoid
> lengthening this page. If we describe every little detail, then it
> becomes long -- just like SubmittingPatches -- and everybody will skip
> reading it.
Good point. How about cutting it down to this then:
--- patch-format.html.orig 2004-08-31 17:30:55.867029816 +0100
+++ patch-format.html 2004-08-31 18:16:14.042804288 +0100
@@ -81,7 +81,9 @@
This cannot be stressed enough. Even when you are resending a change
for the 5th time, resist the urge to attach 20 patches to a single
-email.
+email. If you do send multiple emails though, make sure the second
+and subsequent emails are sent as replies to the first, to keep them
+all together in a thread.
</li><li><h2>Sign your work</h2>
--
dwmw2
next prev parent reply other threads:[~2004-08-31 17:24 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
2004-08-31 17:15 ` Jeff Garzik
2004-08-31 17:17 ` David Woodhouse [this message]
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=1093972632.6200.50.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