From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] History of TUHS
Date: Thu, 16 Jan 2020 20:48:34 -0700 [thread overview]
Message-ID: <7777413e-9e7d-0338-19b3-9392391ecbe9@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20200116220121.GA29855@minnie.tuhs.org>
[-- Attachment #1: Type: text/plain, Size: 176 bytes --]
On 1/16/20 3:01 PM, Warren Toomey wrote:
> Let me know if you have other questions.
Is it worth mentioning COFF anywhere in there?
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]
next prev parent reply other threads:[~2020-01-17 3:49 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 [this message]
2020-01-17 6:51 ` Warren Toomey
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=7777413e-9e7d-0338-19b3-9392391ecbe9@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.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).