From: "Ronald Natalie" <ron@ronnatalie.com>
To: "Wesley Parish" <wobblygong@gmail.com>,
"Warren Toomey via TUHS" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] In case you haven't heard yet
Date: Tue, 03 May 2022 07:16:37 +0000 [thread overview]
Message-ID: <emff74abb5-1131-4aa4-99df-466a1cc5796d@86b94e87.com> (raw)
In-Reply-To: <902481c5-b4c2-7542-5fcd-1c5a619535b6@gmail.com>
Ah yes, when I worked for Rutgers we got the spiel on NeXT (which we
jokingly called Knee-Zit taking the cue from the KneeWiss product from
Sun). It was several years later that one showed up at my office in a
private company (we had also subscribed to callilng the company
“eventually”). I think I remember after dinking with it a few days,
we just stole the memory out of it and stuck it in one of our Suns.
prev parent reply other threads:[~2022-05-03 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 0:57 Wesley Parish
2022-05-03 7:16 ` Ronald Natalie [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=emff74abb5-1131-4aa4-99df-466a1cc5796d@86b94e87.com \
--to=ron@ronnatalie.com \
--cc=tuhs@minnie.tuhs.org \
--cc=wobblygong@gmail.com \
/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).