mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Bob Johnston <haloman@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: undeprecate raw driver.
Date: Mon, 14 May 2007 10:07:57 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705140957370.12444@localhost.localdomain> (raw)
In-Reply-To: <loom.20070514T153159-406@post.gmane.org>

On Mon, 14 May 2007, Bob Johnston wrote:

> Alan Cox <alan <at> lxorguk.ukuu.org.uk> writes:
>
> > > Why not just use the terms:
> > > * outdated - as a replacement for "deprecated".
> >
> > Because they don't actually mean the same thing ?
>
> "superseded" would probably be a better word, perhaps lacking the
> negative connotations of "deprecated"

except that you *want* the negative connotation associated with the
word "deprecated."  you don't just want to say something's been
superseded.  rather, you want to say that it's not only been
superseded but that you really want people to *stop using it* and move
up to the newer version; otherwise, there is no motivation to upgrade.

i'm just baffled by the resistance to the word "deprecated" since it
represents *exactly* the idea you want to get across here.  its use
in software projects is well-established.  why are some people so put
off by it?

> I'm just trying to propose an alternative because it seems that
> deprecated/obsolete causes some confusion.

no, it does *not* cause confusion.  by now, everyone who's been
following this thread knows *exactly* what those two words are being
proposed to represent.  what's happening is that they don't *like*
that proposed usage.

quite simply, there is no confusion here, there is simply annoying
obstinacy.  there's a difference.

rday

-- 
========================================================================
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-14 14:08 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
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 [this message]
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.0705140957370.12444@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=haloman@gmail.com \
    --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®