From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Problems with incremental send/receive
Date: Fri, 10 Jan 2014 16:26:33 +0000 (UTC) [thread overview]
Message-ID: <pan$77172$984d3ca3$b9ceaed1$a8af8577@cox.net> (raw)
In-Reply-To: CAFTPBcKCZwoYoFFOsU3Jg6Cc1evQVOvJ-tjLqDufEaNkx=XkhA@mail.gmail.com
Felix Blanke posted on Fri, 10 Jan 2014 14:15:07 +0100 as excerpted:
> Hi Want,
[snip]
> On Fri, Jan 10, 2014 at 9:02 AM, Wang Shilong
OT, but...
In language circles that's commonly known as a Cupertino, named for the
fact that some older spellcheckers didn't know the word cooperation, and
would suggest replacing it with Cupertino (the city), instead of the dash-
compounded co-operation.
So an inappropriate (and often amusing) spellcheck correction is known as
a Cupertino, with the phenomenon known as the Cupertino effect.
http://en.wiktionary.org/wiki/Cupertino_effect
(I personally would have named it an "allot", the frequent but
inappropriate suggestion to replace the informal "alot", where the
suggestion /should/ be the more acceptable "a lot", since that's the case
where I first became aware of the phenomenon, and I see "allot" used in
the "alot" context frequently enough that I know I'm definitely not the
only one to have the problem.)
(See also Mondegreen, Snowclone, and Crashblossom (this one too new to
appear in wiktionary apparently, but google has it), other christened
phenomena of common modern language mistakes.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-01-10 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 22:04 Problems with incremental send/receive Felix Blanke
2014-01-09 2:10 ` Wang Shilong
2014-01-09 11:36 ` Felix Blanke
2014-01-10 7:26 ` Felix Blanke
2014-01-10 8:02 ` Wang Shilong
2014-01-10 13:15 ` Felix Blanke
2014-01-10 16:26 ` Duncan [this message]
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='pan$77172$984d3ca3$b9ceaed1$a8af8577@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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