From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>, sup-talk <sup-talk@rubyforge.org>
Subject: sup 0.16.0 released
Date: Fri, 21 Mar 2014 16:00:20 +0100 [thread overview]
Message-ID: <1395413618-sup-4468@qwerzila> (raw)
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
Greetings,
I just released sup 0.16.0, get it at rubygems:
$ gem install sup
release notes:
* sup-sync-back-mbox removed.
* safer mime-view attachment file name handling
* show thread labels in thread-view-mode
* remove lock file if there is no sup alive
* deprecate migration script on ruby > 2.1
Cheers, Gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2014-03-21 15:01 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=1395413618-sup-4468@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