From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: v8 /etc/motd
Date: Wed, 09 Aug 2023 10:27:02 -0400 [thread overview]
Message-ID: <940A46E5CF5870F77451F485D89E3698.for-standards-violators@oclsc.org> (raw)
In-Reply-To: <CAP6exYLKYFXpvLAQgOYXFk9SrmOBHTJz3SWdy38m=mGU63dQjg@mail.gmail.com>
On August 8, 2023 3:25:02 p.m. EDT, ron minnich <rminnich@gmail.com> wrote:
>was this one person or a group effort. It's wonderful.
Sorry, if we told you we'd have to sue you.
Norman Wilson, IANAL
Toronto ON
next prev parent reply other threads:[~2023-08-09 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:25 [TUHS] " ron minnich
2023-08-08 19:44 ` [TUHS] " Ron Natalie
2023-08-08 20:00 ` ron minnich
2023-08-09 22:43 ` Kenneth Goodwin
2023-08-09 14:27 ` Norman Wilson [this message]
2023-08-10 1:03 ` Bakul Shah
2023-08-10 8:16 Steve Simon
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=940A46E5CF5870F77451F485D89E3698.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--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).