From: Andi Kleen <andi@firstfloor.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Amanda McPherson" <amanda@amcpherson.com>,
"Jiri Kosina" <jkosina@suse.cz>,
"Roland Dreier" <rdreier@cisco.com>,
"Alex Chiang" <achiang@hp.com>,
"Jochen Voß" <jochen.voss@googlemail.com>
Subject: Re: [PATCH] A development process document, V2
Date: Fri, 08 Aug 2008 12:34:37 +0200 [thread overview]
Message-ID: <87y7374wxu.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080731111443.2179bf4c@bike.lwn.net> (Jonathan Corbet's message of "Thu, 31 Jul 2008 11:14:43 -0600")
Jonathan Corbet <corbet@lwn.net> writes:
> Here is an updated version of the development process document;
> hopefully I've done a reasonable job of addressing everybody's
> comments. Please let me know if you find anything else in need of
> attention.
FWIW I wrote a paper/presentation for this years OLS with many
similar recommendations. The main focus was on strategies for
getting difficult patches in, but it also covered many basics.
http://halobates.de/on-submitting-patches.pdf
http://halobates.de/on-submitting-patches-pres.pdf
If there's interest material from the paper could be reused
or put into Documentation.
-Andi
prev parent reply other threads:[~2008-08-08 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 17:14 [PATCH] A development process document, V2 Jonathan Corbet
2008-07-31 17:17 ` [PATCH] A development process document, V2 (diff from V1) Jonathan Corbet
2008-08-01 11:24 ` Stefan Richter
2008-07-31 20:25 ` [PATCH] A development process document, V2 Chris Friesen
2008-08-04 22:45 ` Jonathan Corbet
2008-08-07 2:30 ` Rob Landley
2008-08-01 19:48 ` Simon Arlott
2008-08-04 13:17 ` Adrian Bunk
2008-08-04 22:40 ` Jonathan Corbet
2008-08-08 7:58 ` Alex Chiang
2008-08-08 10:34 ` Andi Kleen [this message]
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=87y7374wxu.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=amanda@amcpherson.com \
--cc=corbet@lwn.net \
--cc=jkosina@suse.cz \
--cc=jochen.voss@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/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