From: Jan Engelhardt <jengelh@computergmbh.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Grozdan Nikolov <microchip@chello.be>,
Bernd Petrovitsch <bernd@firmix.at>,
linux-kernel@vger.kernel.org
Subject: Re: How innovative is Linux?
Date: Mon, 25 Jun 2007 18:42:24 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706251841420.3137@fbirervta.pbzchgretzou.qr> (raw)
In-Reply-To: <20070625093712.850557f8.rdunlap@xenotime.net>
On Jun 25 2007 09:37, Randy Dunlap wrote:
>On Mon, 25 Jun 2007 17:15:50 +0200 (CEST) Jan Engelhardt wrote:
>> On Jun 25 2007 11:12, Lennart Sorensen wrote:
>> >
>> >It is also quite likely the reply was written before reading the other
>> >comments. With the volume on lkml, reading all comments in a thread
>> >before writing any replies is just not possible.
>>
>> Perhaps the list needs to be split up, e.g. linux-politics@vger :)
>
>I'm for that (including a place for GPL discussions), but I think that
>people would still just overload lkml instead of using the split lists.
Then turn it around: the technical part becomes a separate list. Sort of like
netfilter and netfilter-devel.
Jan
--
next prev parent reply other threads:[~2007-06-25 16:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 12:17 How innovative is Linux? Grozdan Nikolov
2007-06-23 14:43 ` Alan Cox
2007-06-23 15:22 ` Grozdan Nikolov
2007-06-23 15:46 ` Alan Cox
2007-06-23 16:12 ` Torsten Duwe
2007-06-23 16:19 ` Grozdan Nikolov
2007-06-23 16:42 ` Torsten Duwe
2007-06-23 16:54 ` Matthew Jacob
2007-06-23 17:30 ` jimmy bahuleyan
2007-06-23 17:49 ` Diego Calleja
2007-06-23 19:23 ` Alan Cox
2007-06-23 21:02 ` Al Viro
2007-06-23 22:13 ` Alan Cox
2007-06-23 18:12 ` Jan Engelhardt
2007-06-23 19:44 ` Alan Cox
2007-06-23 17:38 ` Benny Amorsen
2007-06-23 19:18 ` Jeffrey V. Merkey
2007-06-23 18:36 ` Grozdan Nikolov
2007-06-24 4:31 ` Rik van Riel
2007-06-23 22:02 ` Carlo Wood
2007-06-23 22:16 ` David Kane
[not found] ` <345c044f0706231513u46d870es6539bdf5797b305b@mail.gmail.com>
2007-06-23 22:27 ` Alan Cox
2007-06-25 9:39 ` Hiro Yoshioka
2007-06-25 22:57 ` Adrian Bunk
2007-06-24 21:36 ` Nikita Danilov
2007-06-23 18:02 ` Satyam Sharma
2007-06-23 18:17 ` Grozdan Nikolov
2007-06-23 17:53 ` Bernd Petrovitsch
2007-06-23 18:15 ` Grozdan Nikolov
2007-06-23 18:54 ` jimmy bahuleyan
2007-06-23 19:06 ` Grozdan Nikolov
2007-06-23 23:15 ` Jesper Juhl
2007-06-25 15:12 ` Lennart Sorensen
2007-06-25 15:15 ` Jan Engelhardt
2007-06-25 16:37 ` Randy Dunlap
2007-06-25 16:42 ` Jan Engelhardt [this message]
2007-06-25 17:51 ` jimmy bahuleyan
2007-06-26 12:26 ` Helge Hafting
2007-06-23 17:43 Al Boldi
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=Pine.LNX.4.64.0706251841420.3137@fbirervta.pbzchgretzou.qr \
--to=jengelh@computergmbh.de \
--cc=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=microchip@chello.be \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for NNTP newsgroup(s).