From: Ian Molton <spyro@f2s.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: viro@math.psu.edu, xavier.bestel@free.fr, linux-kernel@vger.kernel.org
Subject: Re: devfs
Date: Tue, 12 Nov 2002 11:08:34 +0000 [thread overview]
Message-ID: <20021112110834.01e8f2da.spyro@f2s.com> (raw)
In-Reply-To: <20021112104650.GA322@suse.de>
On Tue, 12 Nov 2002 10:46:50 +0000
Dave Jones <davej@codemonkey.org.uk> wrote:
> > And since when did feature freeze affect, as the guy said, *purely*
> > userspace implementations?
>
> Since it would a *feature* to move it out of kernel space.
> To reiterate : _FEATURE_ _FREEZE_. Nothing[1] new[2]
> should be going into mainline at this point.
nothing new WOULD be going in. nor would devfs need to move out - just
disable it. It *is* still an option, is it not?
> We should now be in the stabilising period, where we don't require
> testers to have to upgrade their userspace every fortnight.
its not a kernel issue anymore, if its totally in userspace, is it?
next prev parent reply other threads:[~2002-11-12 11:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 9:32 devfs Ian Molton
2002-11-12 9:43 ` devfs Xavier Bestel
2002-11-12 9:49 ` devfs john slee
2002-11-12 10:01 ` devfs Sean Neakums
2002-11-12 12:51 ` devfs Oliver Neukum
2002-11-13 10:48 ` hotplug (was devfs) Nick Craig-Wood
2002-11-13 17:02 ` Greg KH
2002-11-13 18:06 ` Nick Craig-Wood
2002-11-13 18:04 ` Greg KH
2002-11-14 11:46 ` Oliver Neukum
2002-11-12 10:05 ` devfs Xavier Bestel
2002-11-12 10:04 ` devfs Alexander Viro
2002-11-12 10:25 ` devfs Ian Molton
2002-11-12 10:46 ` devfs Dave Jones
2002-11-12 11:08 ` Ian Molton [this message]
2002-11-12 11:24 ` devfs Rando Christensen
2002-11-12 13:30 ` devfs Alexander Viro
2002-11-12 14:53 ` devfs Alan Cox
2002-11-12 15:37 ` devfs Ian Molton
2002-11-12 11:29 ` devfs Helge Hafting
2002-11-12 15:40 ` devfs Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-08-18 9:10 cerberus errors on 2.4.19 (ide dma related) Alexander Viro
2002-08-18 9:16 ` Ed Sweetman
2002-08-18 18:10 ` Ed Sweetman
2002-08-18 18:20 ` Sean Neakums
2002-08-18 18:29 ` Ed Sweetman
2002-08-18 18:36 ` Sean Neakums
2002-08-18 21:53 ` Barry K. Nathan
2002-08-18 22:26 ` devfs Ed Sweetman
2002-08-18 22:47 ` devfs Sean Neakums
2002-08-18 23:03 ` devfs Alexander Viro
2002-08-18 23:15 ` devfs Ed Sweetman
2002-08-21 4:49 ` devfs Richard Gooch
2002-08-21 5:03 ` devfs Ed Sweetman
2002-08-19 1:06 ` devfs Olivier Galibert
2002-08-19 2:01 ` devfs Greg KH
2002-08-18 23:18 ` devfs Barry K. Nathan
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=20021112110834.01e8f2da.spyro@f2s.com \
--to=spyro@f2s.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
--cc=xavier.bestel@free.fr \
/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