From: Dan Callaghan <djc@djc.id.au>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] web site moved to supmua.dev
Date: Fri, 03 Apr 2026 19:47:45 +1100 [thread overview]
Message-ID: <1775205575-sup-3761@honeycomb.djc.id.au> (raw)
In-Reply-To: <1760944109-sup-8909@honeycomb.djc.id.au>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
I am saddened to see GitHub continuing on its downwards
trajectory[1][2]. In order to further reduce dependencies on it, I have
put up a copy of all the Sup git repos on the supmua.dev web site.
https://supmua.dev/git/
It allows anonymous cloning via HTTPS. There is also a very rudimentary
web view of all files and commits, generated by stagit[3] to keep
hosting costs low.
The repos on GitHub and supmua.dev will be kept in sync with each other.
[1] https://www.theregister.com/2026/03/26/github_ai_training_policy_changes/
[2] https://notes.zachmanson.com/copilot-edited-an-ad-into-my-pr/
[3] https://codemadness.org/stagit.html
--
Dan Callaghan <djc@djc.id.au>
--
You received this message because you are subscribed to the Google Groups "The Sup email client" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supmua+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/supmua/1775205575-sup-3761%40honeycomb.djc.id.au.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-04-04 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 7:14 Dan Callaghan
2026-04-03 8:47 ` Dan Callaghan [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=1775205575-sup-3761@honeycomb.djc.id.au \
--to=djc@djc.id.au \
--cc=supmua@googlegroups.com \
/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