From: Peter Samuelson <peter@cadcamlab.org>
To: Taco Witte <mail@tcwitte.myweb.nl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: modular kernel
Date: Sat, 4 Nov 2000 14:26:20 -0600 [thread overview]
Message-ID: <20001104142620.N1041@wire.cadcamlab.org> (raw)
In-Reply-To: <m13s4Pi-000leyC@green.nl.gxn.net>
In-Reply-To: <m13s4Pi-000leyC@green.nl.gxn.net>; from mail@tcwitte.myweb.nl on Sat, Nov 04, 2000 at 03:38:15PM +0100
[yes I feed trolls sometimes, it's fun]
[Taco Witte]
> Some days ago, I read about the idea of a completely modular kernel.
> I think it's a very good idea, because it would make it easier to get
> more people work at the same moment, development would go faster.
I contend that the barrier to entry is already quite low, as proven by
the fact that *I* contribute to kernel development, albeit rather
little. What evidence do you have to the contrary?
> It would be possible to make groups for a certain part of the kernel
> (for example sound, or filesystems, or main) with own group pages
> with status info and todo's and own mailinglists (it would divide
> this enourmous flow of mail into smaller parts).
Run the following command in the Linux source directory:
grep '^[LW]:' MAINTAINERS | sort -u | more
Then come back with your hot new ideas about having different mailing
lists and web pages for each subsystem.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-04 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-04 14:38 Taco Witte
2000-11-04 20:26 ` Peter Samuelson [this message]
2000-11-04 21:09 ` FORT David
2000-11-04 20:19 ` Doug McNaught
2000-11-06 12:21 ` Horst von Brand
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=20001104142620.N1041@wire.cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@tcwitte.myweb.nl \
/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®