From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: Looks like those boys have a copy of the OED arround
Date: Wed, 16 Oct 1996 17:40:08 -0400 [thread overview]
Message-ID: <19961016214008.pyHEj21a52XZE0tCvliNlvZ8_IEDG7w9yw6sFFIaWvg@z> (raw)
"Tom Glinos, x4302" <tg@utstat.toronto.edu> writes:
| portmanteau?
| hermeneutics?
|
| Hmmm. It seems that Plan 9 and its ilk may be generating a renaissance
| of the English language as well as computing.
Don't get Rob started on "prepend" again.
By the way, if the mnt driver starts complaining about replies not
matching requests is that indicative of a bug? I started getting those
messages in response to attempted network connections when our telecom
people decided to randomize the routing tables for the night.
next reply other threads:[~1996-10-16 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-16 21:40 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-10-16 23:22 philw
1996-10-16 21:47 Russ
1996-10-16 20:55 Tom
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=19961016214008.pyHEj21a52XZE0tCvliNlvZ8_IEDG7w9yw6sFFIaWvg@z \
--to=9fans@9fans.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).