From: Dan Callaghan <djc@djc.id.au>
To: supmua <supmua@googlegroups.com>
Subject: release 1.0 (was: Re: release 0.23)
Date: Sun, 12 Jul 2020 10:59:31 +1000 [thread overview]
Message-ID: <1594515477-sup-4851@sage.djc.id.au> (raw)
In-Reply-To: <1594452938-sup-3097@sage.djc.id.au>
Excerpts from Dan Callaghan's message of 2020-07-11 17:42:37 +10:00:
> I'm pleased to announce that, after quite a long hiatus, Sup 0.23 has
> been released.
It was bugging me that Sup is still calling itself 0.x after all these
years. So I decided to re-release 0.23 with a version number of 1.0. The
new 1.0 release is on Rubygems and Github now. The code is identical to
the 0.23 release.
--
Dan Callaghan <djc@djc.id.au>
prev parent reply other threads:[~2020-07-12 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 7:42 release 0.23 Dan Callaghan
2020-07-11 13:44 ` [sup] " Iain Parris
2020-07-12 0:59 ` 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=1594515477-sup-4851@sage.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