From: Rich Salz <rich.salz@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SunOS4.1.3, etc., on GitHub
Date: Sat, 29 Oct 2022 16:55:54 -0400 [thread overview]
Message-ID: <CAFH29tpTGfMGVo0F=O6JWiLp0VGRY3frTumJ0Tiso1aPUKa-=A@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfq194XcV4+XTvtgLFLSxXixMS8KBm1UhDfCjxUg9jSiEQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
> Sadly, this doesn't appear to be the case. There's no SCCS files that I
> can find. Am I blind?
>
I didn't look or verify anything. Larry also said no SCCS, so you're
probably right. Maybe contact the author.
[-- Attachment #2: Type: text/html, Size: 804 bytes --]
next prev parent reply other threads:[~2022-10-29 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 17:41 [TUHS] " Rich Salz
2022-10-29 19:38 ` [TUHS] " segaloco via TUHS
2022-10-29 19:54 ` Grant Taylor via TUHS
2022-10-29 20:37 ` Warner Losh
2022-10-29 20:55 ` Rich Salz [this message]
2022-10-29 21:40 ` Warner Losh
2022-10-29 21:46 ` Dave Horsfall
2022-10-30 0:12 ` Rich Salz
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='CAFH29tpTGfMGVo0F=O6JWiLp0VGRY3frTumJ0Tiso1aPUKa-=A@mail.gmail.com' \
--to=rich.salz@gmail.com \
--cc=imp@bsdimp.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).