From: Erik Mouw <erik@harddisk-recovery.com>
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:28 +0200 [thread overview]
Message-ID: <20040831161728.GE17261@harddisk-recovery.com> (raw)
In-Reply-To: <413431F5.9000704@pobox.com>
On Tue, Aug 31, 2004 at 04:08:21AM -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
Looks good.
> This URL should be permanent, feel free to bookmark it.
> Comments welcome.
What about including this in the kernel tarball itself so it can't get
lost? You could include it in Documentation/SubmittingPatches.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2004-08-31 16:17 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 [this message]
2004-08-31 16:37 ` David Woodhouse
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=20040831161728.GE17261@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--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