From: Warren Toomey <wkt@tuhs.org>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] History of TUHS
Date: Fri, 17 Jan 2020 16:51:49 +1000 [thread overview]
Message-ID: <20200117065149.GA4002@minnie.tuhs.org> (raw)
In-Reply-To: <7777413e-9e7d-0338-19b3-9392391ecbe9@spamtrap.tnetconsulting.net>
On Thu, Jan 16, 2020 at 08:48:34PM -0700, Grant Taylor via TUHS wrote:
> Is it worth mentioning COFF anywhere in there?
Hmm, I'm not sure. Based on the mailing list archive at
https://minnie.tuhs.org/pipermail/coff/, I set it up in
July 2018 so that us old farts can talk about old computers
when the topic was not strictly Unix-related.
Cheers, Warren
next prev parent reply other threads:[~2020-01-17 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 20:52 Warner Losh
2020-01-16 22:01 ` Warren Toomey
2020-01-17 3:48 ` Grant Taylor via TUHS
2020-01-17 6:51 ` Warren Toomey [this message]
2020-01-17 5:46 ` Lars Brinkhoff
2020-01-17 10:23 Jason Stevens
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=20200117065149.GA4002@minnie.tuhs.org \
--to=wkt@tuhs.org \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@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).