From: "mirabilos" <eccesys@topmail.de>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: deregister?
Date: Mon, 30 Apr 2001 11:39:28 -0000 [thread overview]
Message-ID: <000001c0d24b$9864d8e0$de00a8c0@homeip.net> (raw)
In-Reply-To: <p05100300b712a75c31b2@[207.213.214.37]>
> >>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"?
> At 10:03 PM -0400 2001-04-29, Andres Salomon wrote:
> >Americans can spell? Since when?
>
> OED 2nd Ed:
>
> deregister. v. trans. To remove from a register. Hence
> deregistration. (first citation 1925)
>
> unregistered. ppl. a. Not entered in a register; unrecorded. (first
> citation 1604)
>
> The OED has no entry for "unregister".
My DCE here has no opposite word, just register, but because
register comes from Latin registrare, and due to the DCE's
explanation of how to build opposite words, I'd rather
prefer deregister over disregister over unregister.
A message of love and openness: translate linux into Latin!
It has strict grammar, no such problems, and a single
person on top - the pope, actually. We could replace
his function by Linus ;-) or Alan... dunno
-mirabilos
next prev parent reply other threads:[~2001-05-01 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` mirabilos [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 1:10 deregister? Andres Salomon
2001-04-30 1:27 ` deregister? Rik van Riel
2001-04-30 2:03 ` deregister? Andres Salomon
2001-04-30 1:28 ` deregister? Gregory Maxwell
2001-04-30 4:40 ` deregister? Paul Fulghum
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='000001c0d24b$9864d8e0$de00a8c0@homeip.net' \
--to=eccesys@topmail.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®