From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: undeprecate raw driver.
Date: Sun, 13 May 2007 12:46:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705131239200.942@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0705131835110.9570@yvahk01.tjqt.qr>
On Sun, 13 May 2007, Jan Engelhardt wrote:
>
> On May 13 2007 12:32, Dave Jones wrote:
>
> >Despite repeated attempts over the last two and half years, this
> >driver seems somewhat persistant. Remove its deprecated status as
> >it has existing users who may not be in a position to migrate their
> >apps
>
> At least keep the "it's obsolete" Kconfig description. We don't want
> new users/projects to jump on /dev/raw.
i just *know* this is a mistake, but i'm going to take one more shot
at distinguishing between deprecated and obsolete.
as i understand it, the raw driver is *deprecated*. that is, it's
still there, it's still supported, people are still using it but its
use is *seriously* discouraged and everyone should be trying to move
off of it at their earliest possible convenience.
that is *not* the same as "obsolete" which should mean that that
feature is dead, dead, DEAD and *no one* should be using it anymore.
yes, i realize it sounds like splitting hairs, but it's this malleable
definition of "deprecated" that's causing all of this trouble in the
first place -- the fact that the raw driver is currently listed as
"obsolete" when it is, in fact, only deprecated.
in short, do *not* remove its "deprecated" status. rather, remove its
"obsolete" status and *make* it deprecated.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-13 16:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 16:32 Dave Jones
2007-05-13 16:35 ` Jan Engelhardt
2007-05-13 16:43 ` Dave Jones
2007-05-13 16:46 ` Robert P. J. Day [this message]
2007-05-13 17:34 ` Bernd Eckenfels
2007-05-13 17:56 ` Robert P. J. Day
2007-05-13 20:06 ` Stefan Richter
2007-05-13 20:24 ` Robert P. J. Day
2007-05-13 21:40 ` Stefan Richter
2007-05-13 20:10 ` Stefan Richter
2007-05-13 21:49 ` Tilman Schmidt
2007-05-13 22:42 ` Stefan Richter
2007-05-13 23:01 ` Bob Johnston
2007-05-14 11:42 ` Alan Cox
2007-05-14 13:53 ` Bob Johnston
2007-05-14 14:07 ` Robert P. J. Day
2007-05-15 2:47 ` David Schwartz
2007-05-14 13:39 ` Bill Davidsen
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.0705131239200.942@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=davej@redhat.com \
--cc=jengelh@linux01.gwdg.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®