From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9front@9front.org, Kurt H Maier <khm@sciops.net>
Subject: Re: [9front] Expired SSL certificate
Date: Sun, 07 Apr 2024 09:47:30 -0700 [thread overview]
Message-ID: <5f0b967c15681b0e@orthanc.ca> (raw)
In-Reply-To: <ZhICZuuNfpq2wZBh@wopr>
Kurt H Maier writes:
> More or less antisocial than just taking the server down?
If the hg tree is dead and the commit history is also available
in git, then yes, I would say decommissioning hg is the right
thing to do. That way, if newcomers are exploring for Plan 9
code, they won't be mislead by ancient creaky code.
This frustrated me with Plan9port for a long time. 37+ different
repos ... which one do I believe?
--lyndon
next prev parent reply other threads:[~2024-04-07 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 15:04 mrunix00
2024-04-06 18:29 ` Kurt H Maier
2024-04-07 0:41 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-04-07 0:49 ` Stanley Lieber
2024-04-07 2:18 ` Kurt H Maier
2024-04-07 16:47 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2024-04-07 17:02 ` Kurt H Maier
2024-04-07 17:33 ` Stanley Lieber
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=5f0b967c15681b0e@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9front@9front.org \
--cc=khm@sciops.net \
/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).