From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Bernd Eckenfels <ecki@lina.inka.de>, linux-kernel@vger.kernel.org
Subject: Re: undeprecate raw driver.
Date: Sun, 13 May 2007 22:06:23 +0200 [thread overview]
Message-ID: <46476FBF.5010803@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0705131347450.1144@localhost.localdomain>
Robert P. J. Day wrote:
> 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:
> ----------
[...]
> Obsolete:
> --------
>
> "An obsolete element or attribute is one for which there is no
> guarantee of support by a user agent."
Please quote W3C's entire definition of their notion of obsolete:
"An obsolete element or attribute is one for which there is no guarantee
of support by a user agent. Obsolete elements are no longer defined in
the specification, but are listed for historical purposes in the changes
section of the reference manual."
> there. see the difference? why is this so difficult to grok?
[...]
If you apply W3C's term "obsolete" 1:1 to kernel features, then it would
read:
"An obsolete feature is one for which there is no guarantee of support
by a randomly picked kernel release. Obsolete features are no longer
implemented in this release, but are listed for historical purposes in
Documentation/ABI/removed/."
Except that the term "obsolete" is already used differently in the
context of Linux kernel features; see Documentation/ABI/README.
Also, you say "the official definitions of those terms" were defined at
http://www.w3.org/TR/html4/conform.html. That's not quite true. What
you find there are the definitions of those terms as used in the HTML 4
specification. Nothing more.
--
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-05-13 20:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 16:32 undeprecate raw driver 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
2007-05-13 20:06 ` Stefan Richter [this message]
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=46476FBF.5010803@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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