From: john@jfloren.net (John Floren)
Subject: [TUHS] Mushi and Bagu
Date: Wed, 15 Feb 2017 08:04:52 -0700 [thread overview]
Message-ID: <CAL4LZyisjmmjKv7-UjZ63PW0mhP1f4ZcmFkmR1oX+6k5ZPtwQA@mail.gmail.com> (raw)
In-Reply-To: <20170215150139.GC16647@mcvoy.com>
When I studied Japanese in high school, our teacher told us mushi is bug.
Bagu is a literal transliteration that may be more common in actual use,
but mushi certainly means bug.
On Feb 15, 2017 08:01, "Larry McVoy" <lm at mcvoy.com> 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?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170215/5fd4c16e/attachment.html>
next prev parent reply other threads:[~2017-02-15 15:04 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 [this message]
2017-02-15 15:27 ` Steve Nickolas
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=CAL4LZyisjmmjKv7-UjZ63PW0mhP1f4ZcmFkmR1oX+6k5ZPtwQA@mail.gmail.com \
--to=john@jfloren.net \
/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).