From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>, sup-devel <sup-devel@rubyforge.org>
Subject: sup release 0.15.1
Date: Wed, 04 Dec 2013 15:46:13 +0100 [thread overview]
Message-ID: <1386168248-sup-7525@qwerzila> (raw)
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
Hi suppers,
new Sup 0.15.1 is out:
$ gem install sup
apart from mostly minor bugfixes the visible change is that messages in
threads are now sorted last-activity-last in thread-view-mode.
Please refer to the previous release for more information on upgrading:
http://rubyforge.org/pipermail/sup-talk/2013-November/004997.html
Cheers, Gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-12-04 14:46 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=1386168248-sup-7525@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/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