From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Masscomp oops [was: Any Good dmr Anecdotes?]
Date: Sat, 30 Jun 2018 13:37:05 -0400 (EDT) [thread overview]
Message-ID: <20180630173705.8D5C718C095@mercury.lcs.mit.edu> (raw)
> From: Mike Markowski
> a cute, slender gal came into the lab. ... I typed mkfs... On the plus
> side, I ended up marrying the girl.
OK, so now I _have_ to hear the backstory - _when_ did you tell her what
happened? Then? (Maybe she noticed the look on your face once you realized
what you'd done? :-) Later? Never? :-)
Noel
next reply other threads:[~2018-06-30 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 17:37 Noel Chiappa [this message]
2018-06-30 19:13 ` Mike Markowski
-- strict thread matches above, loose matches on Subject: below --
2018-06-30 1:31 [TUHS] Any Good dmr Anecdotes? Larry McVoy
2018-06-30 2:27 ` [TUHS] Masscomp oops [was: Any Good dmr Anecdotes?] Mike Markowski
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=20180630173705.8D5C718C095@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).