From: Dan Callaghan <noreply@github.com>
To: djc@djc.id.au, sup-commits@supmua.dev
Subject: [sup-heliotrope/sup] e80ea6: delete top-level shell.nix symlink
Date: Fri, 27 Mar 2026 20:51:48 -0700 [thread overview]
Message-ID: <sup-heliotrope/sup/push/refs/heads/develop/c39852-beff97@github.com> (raw)
Branch: refs/heads/develop
Home: https://github.com/sup-heliotrope/sup
Commit: e80ea65987671aeedc0e493ba42f7c832e96870b
https://github.com/sup-heliotrope/sup/commit/e80ea65987671aeedc0e493ba42f7c832e96870b
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-03-21 (Sat, 21 Mar 2026)
Changed paths:
M Manifest.txt
R shell.nix
Log Message:
-----------
delete top-level shell.nix symlink
I keep forgetting that it doesn't actually work, because nowadays nix
tries to resolve the reference to gemset.nix relative to the symlink not
its real path.
Commit: 7580318c9d58be5a24b320c0d69a87a319292d2d
https://github.com/sup-heliotrope/sup/commit/7580318c9d58be5a24b320c0d69a87a319292d2d
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-03-28 (Sat, 28 Mar 2026)
Changed paths:
M lib/sup.rb
M test/integration/test_sup-add.rb
Log Message:
-----------
adjust regex for fixing old YAML tag URIs to handle SentLoader
Apparently some old sources.yaml files would have a source like this:
- !supmua.org,2006-10-01/Redwood/SentLoader {}
The regex previously added in commit 1aac9d4388 would fail to fix up an
invalid tag URI like this because of the trailing empty map.
Fixes #516.
Commit: beff97f84382cbcf3494ab1fd87b7b076ee0a2ca
https://github.com/sup-heliotrope/sup/commit/beff97f84382cbcf3494ab1fd87b7b076ee0a2ca
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-03-28 (Sat, 28 Mar 2026)
Changed paths:
M doc/wiki
Log Message:
-----------
update wiki submodule
Deletes the obsolete sup-psych-ify-config-files(1) man page.
Compare: https://github.com/sup-heliotrope/sup/compare/c39852484ff5...beff97f84382
To unsubscribe from these emails, change your notification settings at https://github.com/sup-heliotrope/sup/settings/notifications
reply other threads:[~2026-03-28 3:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sup-heliotrope/sup/push/refs/heads/develop/c39852-beff97@github.com \
--to=noreply@github.com \
--cc=djc@djc.id.au \
--cc=sup-commits@supmua.dev \
/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