From: Greg KH <greg@kroah.com>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Kalin KOZHUHAROV <kalin@thinrope.net>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development
Date: Tue, 15 Nov 2005 11:04:41 -0800 [thread overview]
Message-ID: <20051115190441.GA15033@kroah.com> (raw)
In-Reply-To: <4d8e3fd30511150037j63a479b5j7c38430f9f5ffedd@mail.gmail.com>
On Tue, Nov 15, 2005 at 09:37:58AM +0100, Paolo Ciarrocchi wrote:
> On 11/15/05, Greg KH <greg@kroah.com> wrote:
> > On Tue, Nov 15, 2005 at 09:18:35AM +0900, Kalin KOZHUHAROV wrote:
> > > Greg KH wrote:
> > > > On Mon, Nov 14, 2005 at 02:07:09PM -0800, Greg KH wrote:
> > > >
> > > >>So, I've been working on a document for the past week or so to help
> > > >>alleviate a lot of these problems.
> > > >
> > > >
> > > > Oh, the latest version can be found at:
> > > > http://www.kernel.org/git/?p=linux/kernel/git/gregkh/patches.git;a=blob;f=HOWTO
> > > > as I'm keeping it in my git patch tree.
> > >
> > > As far as the development proces is in TODO state, what about adding
> > > Paolo Ciarrocchi's (CCed) doc there?
> > > http://linux.tar.bz/articles/2.6-development_process
> >
> > Ah, a very nice summary.
> >
> > Paolo, can I use this document as a base for this section in the HOWTO
> > file (with proper attribution of course.)
>
> Yup!
> Of course you can.
Great, thanks for letting me borrow from you.
I'll have an update based on all of the feedback, and Paolo's article
soon.
greg k-h
next prev parent reply other threads:[~2005-11-15 19:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:07 [RFC] HOWTO do Linux kernel development Greg KH
2005-11-14 22:10 ` Greg KH
2005-11-14 22:43 ` [RFC] [HUMOR] " Jeffrey V. Merkey
2005-11-15 0:18 ` [RFC] " Kalin KOZHUHAROV
2005-11-15 0:32 ` Randy.Dunlap
2005-11-15 4:58 ` Greg KH
2005-11-15 8:37 ` Paolo Ciarrocchi
2005-11-15 19:04 ` Greg KH [this message]
2005-11-15 0:32 ` Josh Boyer
2005-11-15 1:25 ` Paul Jackson
2005-11-15 1:31 ` Randy.Dunlap
2005-11-15 2:16 ` Josh Boyer
2005-11-15 2:42 ` Paul Jackson
2005-11-15 2:52 ` Josh Boyer
2005-11-15 3:01 ` Paul Jackson
2005-11-15 4:48 ` Greg KH
2005-11-15 4:47 ` Greg KH
2005-11-15 1:08 ` Coywolf Qi Hunt
2005-11-15 4:38 ` Greg KH
2005-11-15 5:51 ` Coywolf Qi Hunt
2005-11-15 5:52 ` Greg KH
2005-11-15 6:31 ` Coywolf Qi Hunt
2005-11-17 13:54 ` Pavel Machek
2005-11-15 14:42 ` Andi Kleen
2005-11-15 17:33 ` Greg KH
2005-11-16 8:12 ` Michael Kerrisk
2005-11-17 6:56 ` Greg KH
2005-11-17 12:12 ` Michael Kerrisk
2005-11-15 20:10 ` Luca
2005-11-15 20:13 ` Josh Boyer
2005-11-15 20:56 ` Greg KH
2005-11-16 4:38 ` Randy.Dunlap
2005-11-15 22:20 ` sitexec
-- strict thread matches above, loose matches on Subject: below --
2005-11-16 12:15 linux
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=20051115190441.GA15033@kroah.com \
--to=greg@kroah.com \
--cc=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.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