From: Mike Bell <mike@mikebell.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: linux@horizon.com, linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu
Subject: Re: [GIT PATCH] Remove devfs from 2.6.13
Date: Wed, 14 Sep 2005 13:01:24 -0700 [thread overview]
Message-ID: <20050914200123.GC15017@mikebell.org> (raw)
In-Reply-To: <808CC4DC-15F3-4F6E-A9C6-6CBEC3D5415F@mac.com>
On Sun, Sep 11, 2005 at 11:43:02AM -0400, Kyle Moffett wrote:
> That sounds like _exactly_ the case where the Debian folks could
> maintain the out-of-tree ndevfs patch for a while until they got their
> installer floppies and such migrated to udev.
Then you know nothing about the subject at hand. Moving from devfs to
ndevfs is dramatically /harder/ than moving from devfs to udev. ndevfs
is not devfs compatible in any way, shape or form.
next prev parent reply other threads:[~2005-09-14 20:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 11:44 [GIT PATCH] Remove devfs from 2.6.13 linux
2005-09-11 15:43 ` Kyle Moffett
2005-09-14 20:01 ` Mike Bell [this message]
2005-09-14 20:13 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 21:45 Greg KH
2005-09-10 8:27 ` Mike Bell
2005-09-10 21:52 ` Greg KH
2005-09-10 23:03 ` Mike Bell
2005-09-11 5:09 ` Greg KH
2005-09-12 13:40 ` Steven Rostedt
2005-09-14 20:00 ` Mike Bell
2005-09-14 20:28 ` Kyle Moffett
2005-09-14 23:06 ` Greg KH
2005-09-10 9:03 ` Michael Thonke
2005-09-10 12:32 ` Douglas McNaught
2005-09-10 21:55 ` Greg KH
2005-09-10 14:15 ` J.A. Magallon
2005-09-10 23:24 ` J.A. Magallon
2005-09-10 23:30 ` Greg KH
2005-09-11 0:48 ` David Lang
2005-09-11 3:07 ` Greg KH
2005-09-11 6:08 ` David Lang
2005-09-11 7:05 ` Arjan van de Ven
2005-09-11 7:13 ` Valdis.Kletnieks
2005-09-11 7:20 ` David Lang
2005-09-11 11:02 ` Theodore Ts'o
2005-09-12 8:01 ` Martin Schlemmer
2005-09-11 17:15 ` Greg KH
2005-09-11 11:35 ` Bastian Blank
2005-09-11 11:42 ` CaT
2005-09-11 17:17 ` Greg KH
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=20050914200123.GC15017@mikebell.org \
--to=mike@mikebell.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=mrmacman_g4@mac.com \
/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