From: David Arnold <davida@pobox.com>
To: Angelo Papenhoff <aap@papnet.eu>
Cc: segaloco via TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Fifth Edition Manual Restoration
Date: Thu, 9 Mar 2023 10:09:56 +1100 [thread overview]
Message-ID: <944F23E0-DBB0-45E3-AE08-3CF17AE98426@pobox.com> (raw)
In-Reply-To: <ZAi4M3cnw8xHx7ko@indra.papnet.eu>
> On 9 Mar 2023, at 03:30, Angelo Papenhoff <aap@papnet.eu> wrote:
…
> And even then one would need CAT emulation, which I
> haven't bothered with yet.
That sounds like a fun project — is there really no such beast already?
d
next prev parent reply other threads:[~2023-03-08 23:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 7:26 [TUHS] " segaloco via TUHS
2023-03-08 10:02 ` [TUHS] " Angelo Papenhoff
2023-03-08 16:02 ` segaloco via TUHS
2023-03-08 16:30 ` Angelo Papenhoff
2023-03-08 20:55 ` josh
2023-03-08 22:21 ` segaloco via TUHS
2023-03-08 23:09 ` David Arnold [this message]
2023-03-09 6:59 ` arnold
2023-03-09 14:24 ` Clem Cole
2023-03-09 20:48 ` Rob Pike
2023-03-09 21:04 ` Dave Horsfall
2023-03-09 22:32 ` Rich Salz
2023-03-09 23:51 ` Jeremy C. Reed
2023-03-10 1:58 ` Rob Pike
2023-03-10 6:33 ` Jonathan Gray
2023-03-10 7:50 ` Jonathan Gray
2023-03-10 13:11 ` Clem Cole
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=944F23E0-DBB0-45E3-AE08-3CF17AE98426@pobox.com \
--to=davida@pobox.com \
--cc=aap@papnet.eu \
--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).