From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Mushi and Bagu
Date: Wed, 15 Feb 2017 10:27:13 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.02.1702151025120.84714@frieza.hoshinet.org> (raw)
In-Reply-To: <20170215150139.GC16647@mcvoy.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Wed, 15 Feb 2017, Larry McVoy wrote:
> On Wed, Feb 15, 2017 at 09:51:58AM -0500, Nemo wrote:
>> Follow-up to Larry's "Mushi! Mushi!" story
>> (http://minnie.tuhs.org/pipermail/tuhs/2017-February/008149.html).
>>
>> I showed this to a Japanese acquaintance, who found it hilarious for a
>> different reason. He told me that a s/w bug is "bagu" -- a
>> semi-transliteration -- and "mushi" is "I ignore you". So corporate
>> called, asked for status, and the technical guy said "I am going to
>> ignore you!" and then hung up.
>
> Wow, that's even better than "Bug, bug!". Are you sure? Someone else
> said moshi was hi and mushi was bug. Does mushi have two meanings?
>
If you can believe this the Japanese version of "Pok��mon" occasionally
puns on the dual meaning of "mushi" - ��ϟoҕ ("mushi wa mushi", more or
less, "the bugs don't bug me").
-uso.
next prev parent reply other threads:[~2017-02-15 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:51 Nemo
2017-02-15 15:01 ` Larry McVoy
2017-02-15 15:04 ` John Floren
2017-02-15 15:27 ` Steve Nickolas [this message]
2017-02-15 15:30 Noel Chiappa
2017-02-15 16:13 ` Nick Downing
2017-02-15 18:16 ` Nemo
2017-02-16 7:28 Rudi Blom
2017-02-16 9:36 ` jsteve
2017-02-16 10:42 ` Nick Downing
2017-02-16 13:49 ` Rudi Blom
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=alpine.BSF.2.02.1702151025120.84714@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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;
as well as URLs for NNTP newsgroup(s).