From: Dan Cross <crossd@gmail.com>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: Joining COFF mailing list
Date: Sat, 25 Mar 2023 12:07:15 -0400 [thread overview]
Message-ID: <CAEoi9W6KRbrs8fTgDgkVkdi7ueYbfow0tQJWgYooMb=8U1BBFw@mail.gmail.com> (raw)
In-Reply-To: <CAJXSPs-vkeSNWoU4ESohSSQ8OysoWXSZ2OV3LdE93CN0SrFx0w@mail.gmail.com>
On Sat, Mar 25, 2023 at 11:34 AM KenUnix <ken.unix.guy@gmail.com> wrote:
> Matt G. suggested that I join the COFF mailing list.
>
> He thought it might be a better site to post my questions
> operational and technical ..
I don't know if that's the best place, actually.
I think I'd recommend the 'cctalk' mailing list:
https://classiccmp.org/mailman3/postorius/lists/cctalk.classiccmp.org/
That is active with folks working on running and emulating classic
computers, and I think you would find it a good source of information
of the type your posts lead me to believe you're after.
- Dan C.
prev parent reply other threads:[~2023-03-25 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJXSPs-Fw3biRRfh4ey0T61pAuTgqFFigqDCncMsieoDDPu+Yg@mail.gmail.com>
2023-03-25 15:34 ` [TUHS] " KenUnix
2023-03-25 16:07 ` Dan Cross [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='CAEoi9W6KRbrs8fTgDgkVkdi7ueYbfow0tQJWgYooMb=8U1BBFw@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=ken.unix.guy@gmail.com \
--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).