From: hpa@zytor.com
To: "Adrian Bunk" <bunk@fs.tum.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: A users thoughts on the new dev. model
Date: Fri, 23 Jul 2004 16:04:32 -0700 (PDT) [thread overview]
Message-ID: <32791.66.11.168.47.1090623872.squirrel@www.zytor.com> (raw)
In-Reply-To: <20040723214055.GR19329@fs.tum.de>
>
> One problem from a user's point of view is that removal of obsolete code
> that works sufficiently for some users.
>
> Andrew said explicitely in a mail to linux-kernel that he'd consider
> removing devfs "mid-2005" - and it didn't sound as if this would only be
> a -mm "feature".
>
> Even if 2.7 is started this doesn't has to imply that it has to be
> flooded with big changes - a short 2.7 with relativley few invasive
> changes might also be an option.
>
There is no difference from a user's point of view between a "short 2.7"
and "a close -mm tree." Either way devfs is on death row, because it's
buggy and unmaintained. Any piece of code, *especially* one as invasive
as devfs, which is buggy and unmaintained is a hassle to for *all* kernel
development, and have to be extricated at some point.
-hpa
next prev parent reply other threads:[~2004-07-23 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 15:04 Evan Hisey
2004-07-22 22:25 ` Bill Davidsen
2004-07-23 13:58 ` H. Peter Anvin
2004-07-23 15:24 ` szonyi calin
2004-07-23 16:39 ` David Ford
2004-07-23 19:06 ` Xiong Jiang
2004-07-23 20:00 ` Tim Wright
2004-07-23 21:40 ` Adrian Bunk
2004-07-23 23:04 ` hpa [this message]
2004-07-24 10:38 ` Adrian Bunk
2004-07-27 20:08 ` Bill Davidsen
2004-07-22 22:57 ` Paul Jackson
2004-07-27 20:20 ` Bill Davidsen
2004-07-28 7:31 ` Paul Jackson
2004-07-23 19:32 ` Florin Andrei
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=32791.66.11.168.47.1090623872.squirrel@www.zytor.com \
--to=hpa@zytor.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.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®