From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Giacomo A. Catenazzi" <cate@cateee.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Valdis.Kletnieks@vt.edu,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: using LKML for subsystem development
Date: Fri, 01 Feb 2008 20:53:05 +0100 [thread overview]
Message-ID: <47A378A1.4060605@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080201094057.GA27910@elte.hu>
Ingo Molnar wrote:
> and your solution: you advocate destroying information by pulling it off
> lkml
I did not propose to pull anything off of LKML.
I argued that LKML's topic is not a true superset of some of those other
lists' topics, hence cannot truly replace those lists.
--
Stefan Richter
-=====-==--- --=- ----=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-02-01 19:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 23:17 Linux 2.6.24 Linus Torvalds
2008-01-24 23:41 ` Linus Torvalds
2008-01-25 9:10 ` Giacomo A. Catenazzi
2008-01-25 9:58 ` Valdis.Kletnieks
2008-01-25 11:58 ` Rafael J. Wysocki
2008-01-25 12:34 ` Giacomo A. Catenazzi
2008-01-25 23:50 ` Stefan Richter
2008-01-26 0:42 ` using LKML for subsystem development (was Re: Linux 2.6.24) Stefan Richter
2008-01-26 3:28 ` Valdis.Kletnieks
2008-01-26 13:31 ` using LKML for subsystem development Stefan Richter
2008-01-27 7:37 ` Valdis.Kletnieks
2008-01-26 11:28 ` using LKML for subsystem development (was Re: Linux 2.6.24) Ingo Molnar
2008-01-26 14:07 ` using LKML for subsystem development David Miller
2008-01-26 14:45 ` Stefan Richter
2008-01-26 14:25 ` Stefan Richter
2008-02-01 9:40 ` Ingo Molnar
2008-02-01 19:53 ` Stefan Richter [this message]
2008-01-26 3:19 ` Linux 2.6.24 Valdis.Kletnieks
2008-01-25 11:35 ` Ingo Molnar
2008-01-25 10:11 ` [PATCH] linux-2.6.24/drivers/hid/hid-input.c Philipp Matthias Hahn
2008-01-25 10:30 ` Jiri Kosina
2008-02-03 12:35 ` Linux 2.6.24 Jan Engelhardt
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=47A378A1.4060605@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cate@cateee.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®