mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: maturity and status and attributes, oh my!
Date: Sat, 1 Sep 2007 05:54:14 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709010548200.29584@localhost.localdomain> (raw)
In-Reply-To: <46D93544.2030308@s5r6.in-berlin.de>

On Sat, 1 Sep 2007, Stefan Richter wrote:

> Robert P. J. Day wrote:
> > given the possible interpretations of EXPERIMENTAL that i hadn't
> > considered until now, maybe it really *does* make sense to tag
> > something as both EXPERIMENTAL and, say, DEPRECATED (does it?).
>
> In theory maybe, for communication purposes perhaps rather not.
>
> The reasoning why a feature is deprecated will typically include the
> gotchas which caused the feature to be considered experimental, if
> such gotchas still apply.

fair enough. there may be times when people won't agree when something
is actually "deprecated."  but in cases of actual disagreement, the
easiest solution is to do nothing -- leave that feature untagged, it
won't hurt anything.  it would be like arguing about whether something
should currently depend on EXPERIMENTAL.  who cares?  a user can
simply click on whether they want to see EXPERIMENTAL stuff, anyway.

the places where this makes sense is where everyone agrees that
something is now officially deprecated -- like when it gets its own
entry in the features removal file with a scheduled removal date.
once that happens, it's beyond the point of debate.

but so what if something gets mis-classified every so often?  you
always have the ability to ignore all that attribute classification in
the end, anyway.  no harm, no foul.

rday

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

http://crashcourse.ca
========================================================================

  reply	other threads:[~2007-09-01 10:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 21:38 Robert P. J. Day
2007-08-31 22:02 ` Jeff Garzik
2007-09-01  6:35   ` Jan Engelhardt
2007-09-01  9:06     ` Robert P. J. Day
2007-08-31 22:36 ` Stefan Richter
2007-09-01  1:23   ` Robert P. J. Day
2007-09-01  9:14     ` Stefan Richter
2007-09-01  9:21       ` Robert P. J. Day
2007-09-01  9:47         ` Stefan Richter
2007-09-01  9:54           ` Robert P. J. Day [this message]
2007-09-01 13:14           ` Jan Engelhardt
2007-09-01 13:53             ` Jeff Garzik
2007-09-01 10:43       ` Jeff Garzik
2007-09-01 10:52         ` Robert P. J. Day
2007-09-01 11:06           ` Jeff Garzik
2007-09-01 13:44             ` Bartlomiej Zolnierkiewicz
2007-09-01 13:52               ` Jeff Garzik
2007-09-01 14:27               ` Stefan Richter
     [not found]   ` <Pine.LNX.4.64.0709010435070.26137@localhost.localdomain>
2007-09-01  9:27     ` Stefan Richter
2007-09-01  9:41       ` Robert P. J. Day
2007-09-01 17:22         ` Dave Jones
2007-09-01 17:58           ` Robert P. J. Day
2007-09-01 18:06             ` Robert P. J. Day
2007-09-01 18:24               ` Dave Jones
2007-08-31 23:02 ` Dave Jones
2007-09-01  8:34   ` Robert P. J. Day
2007-08-31 23:29 Mitchell Erblich
2007-09-01  1:33 ` Robert P. J. Day
2007-09-01  6:39   ` Jan Engelhardt
2007-09-01  7:02     ` Robert P. J. Day

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.0709010548200.29584@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®