From: Greg KH <greg@kroah.com>
To: Paul Jackson <pj@sgi.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development
Date: Mon, 14 Nov 2005 20:48:12 -0800 [thread overview]
Message-ID: <20051115044812.GD28005@kroah.com> (raw)
In-Reply-To: <20051114190150.2986cb65.pj@sgi.com>
On Mon, Nov 14, 2005 at 07:01:50PM -0800, Paul Jackson wrote:
> Josh wrote:
> > How about this:
>
> Good.
>
> I'd add to the list of "what should you be expecting"
>
> - silence (Some lkml posts are ignored. Improve it and try again.)
Very important to add, thanks for pointing it out.
greg k-h
next prev parent reply other threads:[~2005-11-15 5:12 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
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 [this message]
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=20051115044812.GD28005@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.