Commit notifications for all Sup repositories
 help / color / mirror / Atom feed
From: Dan Callaghan <dan@bl2.djc.id.au>
To: sup-commits@supmua.dev
Subject: [sup-website.git] branch master updated: add ncursesw-ruby git repo
Date: Sun, 11 Oct 2026 14:13:56 +1100	[thread overview]
Message-ID: <179168843664.338049.16432068179760464153@bl2.djc.id.au> (raw)

Pushed a commit to branch master:
https://supmua.dev/git/sup-website/commit/ab70715f4d5037c5add0fcdc82dbe95471cc1674.html

The following commit(s) were added to refs/heads/master by this push:
     new ab70715  add ncursesw-ruby git repo
ab70715 is described below

commit ab70715f4d5037c5add0fcdc82dbe95471cc1674
Author: Dan Callaghan <djc@djc.id.au>
AuthorDate: Sun Oct 11 14:13:21 2026 +1100

    add ncursesw-ruby git repo
---
 _plugins/stagit.rb | 2 +-
 git/index.md       | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/_plugins/stagit.rb b/_plugins/stagit.rb
index b319183..5891936 100644
--- a/_plugins/stagit.rb
+++ b/_plugins/stagit.rb
@@ -53,7 +53,7 @@ end
 
 Jekyll::Hooks.register :site, :post_write do |site|
   header = File.read "#{site.source}/_includes/header.html"
-  %w[sup sup-colors sup-website].each do |repo|
+  %w[sup sup-colors sup-website ncursesw-ruby].each do |repo|
     dest = "#{site.dest}/git/#{repo}"
     Jekyll.logger.info "Stagit:", "Processing #{repo}"
 
diff --git a/git/index.md b/git/index.md
index 8e312a1..cf44ff5 100644
--- a/git/index.md
+++ b/git/index.md
@@ -19,4 +19,5 @@ You can also find [Sup on GitHub](https://github.com/sup-heliotrope/sup).
 ### Other repos
 
 [sup-colors.git](sup-colors/log.html): Color schemes for Sup.<br>
-[sup-website.git](sup-website/log.html): Source code for this web site.
+[sup-website.git](sup-website/log.html): Source code for this web site.<br>
+[ncursesw-ruby.git](ncursesw-ruby/log.html): Ruby bindings to ncurses (Sup’s fork).

                 reply	other threads:[~2026-10-11  3:13 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=179168843664.338049.16432068179760464153@bl2.djc.id.au \
    --to=dan@bl2.djc.id.au \
    --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