From: Dan Callaghan <noreply@github.com>
To: djc@djc.id.au, sup-commits@supmua.dev
Subject: [sup-heliotrope/sup-website] 104c34: fix typo in body font-size
Date: Sun, 19 Oct 2025 04:18:42 -0700 [thread overview]
Message-ID: <sup-heliotrope/sup-website/push/refs/heads/master/25fc39-9bbf79@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/sup-heliotrope/sup-website
Commit: 104c34da2b20ff73891019519bb1dafb798d318b
https://github.com/sup-heliotrope/sup-website/commit/104c34da2b20ff73891019519bb1dafb798d318b
Author: Dan Callaghan <djc@djc.id.au>
Date: 2025-10-12 (Sun, 12 Oct 2025)
Changed paths:
M stylesheets/stylesheet.css
Log Message:
-----------
fix typo in body font-size
Commit: 6e6dd32434021612afffadc317e6a2dce29edc4d
https://github.com/sup-heliotrope/sup-website/commit/6e6dd32434021612afffadc317e6a2dce29edc4d
Author: Dan Callaghan <djc@djc.id.au>
Date: 2025-10-12 (Sun, 12 Oct 2025)
Changed paths:
A stylesheets/public-inbox.css
Log Message:
-----------
add a stylesheet for public-inbox
Mostly copy-pasted from the existing Jekyll theme, to try and keep it
looking consistent.
This file is not directly referenced by its URL, instead it gets served
by public-inbox as minified CSS embedded into the top of every HTML
page.
Commit: 1f0a78b1218e963c725f071324157757b00b0c37
https://github.com/sup-heliotrope/sup-website/commit/1f0a78b1218e963c725f071324157757b00b0c37
Author: Dan Callaghan <djc@djc.id.au>
Date: 2025-10-12 (Sun, 12 Oct 2025)
Changed paths:
M _layouts/default.md
Log Message:
-----------
link to the GitHub repo instead of the org
There is not much of interest to see in the sup-heliotrope GitHub
organisation anymore, besides Sup itself.
Commit: d2ab7f3a46b1e54c2492ebfcf138d2edec846f0d
https://github.com/sup-heliotrope/sup-website/commit/d2ab7f3a46b1e54c2492ebfcf138d2edec846f0d
Author: Dan Callaghan <djc@djc.id.au>
Date: 2025-10-12 (Sun, 12 Oct 2025)
Changed paths:
M _layouts/default.md
Log Message:
-----------
suppress favicon requests
We never had any icon for Sup so there is nothing to put here. This
technique just avoids the browser fetching a multi-kilobyte 404 page
for favicon.ico on every page view.
https://stackoverflow.com/a/13416784/120202
Commit: e57f30ee3979f7c5a839f63129da53e442ad1173
https://github.com/sup-heliotrope/sup-website/commit/e57f30ee3979f7c5a839f63129da53e442ad1173
Author: Dan Callaghan <djc@djc.id.au>
Date: 2025-10-19 (Sun, 19 Oct 2025)
Changed paths:
M _layouts/default.md
R history/index.md
Log Message:
-----------
remove History page
This was not adding much value. The ancient history of Sup is already
well described in other places, like the README and the wiki.
Commit: 9bbf797bbfc7dbbb5fe2c1f19673cb8b52702691
https://github.com/sup-heliotrope/sup-website/commit/9bbf797bbfc7dbbb5fe2c1f19673cb8b52702691
Author: Dan Callaghan <djc@djc.id.au>
Date: 2025-10-19 (Sun, 19 Oct 2025)
Changed paths:
M stylesheets/stylesheet.css
Log Message:
-----------
fix misaligned bulleted lists
Compare: https://github.com/sup-heliotrope/sup-website/compare/25fc39dff23c...9bbf797bbfc7
To unsubscribe from these emails, change your notification settings at https://github.com/sup-heliotrope/sup-website/settings/notifications
reply other threads:[~2025-10-19 11:18 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-website/push/refs/heads/master/25fc39-9bbf79@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