From: "Michael Kjörling" <e5655f30a07f@ewoof.net>
To: tuhs@tuhs.org
Subject: [TUHS] OS and vendor identification
Date: Wed, 29 May 2024 11:57:50 +0000 [thread overview]
Message-ID: <dc8a9c4d-f01f-47c6-b4df-905b941af755@home.arpa> (raw)
I spotted this elsewhere and thought that maybe someone here might be
able to contribute.
https://lists.gnu.org/archive/html/config-patches/2024-05/msg00022.html
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
next reply other threads:[~2024-05-29 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 11:57 Michael Kjörling [this message]
2024-05-29 17:22 ` [TUHS] " Lars Brinkhoff
2024-05-29 17:31 ` Dan Cross
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=dc8a9c4d-f01f-47c6-b4df-905b941af755@home.arpa \
--to=e5655f30a07f@ewoof.net \
--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).