public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@mp3revolution.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: deregister?
Date: Sun, 29 Apr 2001 22:03:19 -0400	[thread overview]
Message-ID: <20010429220319.A18411@mp3revolution.net> (raw)
In-Reply-To: <20010429211049.A17111@mp3revolution.net> <Pine.LNX.4.21.0104292224000.19012-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0104292224000.19012-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Sun, Apr 29, 2001 at 10:27:29PM -0300

On Sun, Apr 29, 2001 at 10:27:29PM -0300, Rik van Riel wrote:
> 
> On Sun, 29 Apr 2001, Andres Salomon wrote:
> 
> > Not to mention in various comments and documentation.  Deregister,
> > according to www.m-w.com (and many other dictionaries), is not a word.
> > Is there some sort of historical significance to this being used, in
> > place of "unregister"?
> 
> Yes, we're all anti-american terrorists who plan to make the
> US economy collapse by inventing lots of new words which will
> have to be added to the dictionary, making the US economy
> unable to support the ever-growing dictionaries and ensuring
> the Americans will be unable to (learn to) spell, leaving them

Americans can spell?  Since when?

> dead in the water if there's ever a linguistic war between
> them and the UK.
> 
> Cunning, isn't it?
> 
> cheers,
> 
> Rik
> --
> Virtual memory is like a game you can't win;
> However, without VM there's truly nothing to lose...
> 
> http://www.surriel.com/		http://distro.conectiva.com/
> 
> Send all your spam to aardvark@nl.linux.org (spam digging piggy)
> 
>

Well, at least you provided a reason. ;P  That would be incredibly lame
if the answer turned out to be, "The original author made a mistake,
and no one cared enough to fix it.  API users (who are constantly
mixing up unregister and deregister) be damned."

-- 
"... being a Linux user is sort of like living in a house inhabited
by a large family of carpenters and architects. Every morning when
you wake up, the house is a little different. Maybe there is a new
turret, or some walls have moved. Or perhaps someone has temporarily
removed the floor under your bed." - Unix for Dummies, 2nd Edition
        -- found in the .sig of Rob Riggs, rriggs@tesser.com

  reply	other threads:[~2001-04-30  2:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30  1:10 deregister? Andres Salomon
2001-04-30  1:27 ` deregister? Rik van Riel
2001-04-30  2:03   ` Andres Salomon [this message]
2001-04-30  1:28 ` deregister? Gregory Maxwell
2001-04-30  4:40 ` deregister? Paul Fulghum
  -- strict thread matches above, loose matches on Subject: below --
2001-04-30  5:23 deregister? Jonathan Lundell
2001-04-30  5:39 ` deregister? Steve VanDevender
2001-04-30  6:03   ` deregister? Jonathan Lundell
2001-04-30 11:39 ` deregister? mirabilos

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=20010429220319.A18411@mp3revolution.net \
    --to=dilinger@mp3revolution.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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