mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: undeprecate raw driver.
Date: Sun, 13 May 2007 13:56:00 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705131347450.1144@localhost.localdomain> (raw)
In-Reply-To: <E1HnHxK-0004CI-00@calista.eckenfels.net>

On Sun, 13 May 2007, Bernd Eckenfels wrote:

> In article <Pine.LNX.4.64.0705131239200.942@localhost.localdomain> you wrote:
> > in short, do *not* remove its "deprecated" status.  rather, remove its
> > "obsolete" status and *make* it deprecated.
>
> it is deprecated and obsolete.

no, it's not.  and, trust me, no one on this list wants me to have to
explain all that again.  :-)

rday

p.s.  before we get into this again where everyone thinks they know
what they're talking about, i suggest consulting the official
definitions of those two terms as defined at
http://www.w3.org/TR/html4/conform.html:

Deprecated:
----------

"A deprecated element or attribute is one that has been outdated by
newer constructs. Deprecated elements are defined in the reference
manual in appropriate locations, but are clearly marked as deprecated.
Deprecated elements may become obsolete in future versions of HTML.

"User agents should continue to support deprecated elements for
reasons of backward compatibility.

"Definitions of elements and attributes clearly indicate which are
deprecated."

  got that?  deprecated means that it's been "outdated," but it's
still defined, it's still supported, it's marked as "deprecated", and
it ***may become*** obsolete in future versions.  if there's a better
description of raw drivers, i don't know where you'd find it.

Obsolete:
--------

"An obsolete element or attribute is one for which there is no
guarantee of support by a user agent."

  there.  see the difference?  why is this so difficult to grok?  you
can be deprecated, or you can be obsolete.  you *can't* be both.  so
please stop making that argument.

p.p.s.  using those definitions, deprecated features are *not*
possible candidates for removal, but obsolete features *are*.  that's
why raw drivers are deprecated, not obsolete.

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-05-13 17:56 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
2007-05-13 17:34     ` Bernd Eckenfels
2007-05-13 17:56       ` Robert P. J. Day [this message]
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.0705131347450.1144@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=ecki@lina.inka.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®