From: Gaute Hope <eg@gaute.vetsj.com>
To: supmua <supmua@googlegroups.com>
Subject: release 0.22.0
Date: Tue, 16 Jun 2015 12:20:59 +0000 [thread overview]
Message-ID: <1434457165-astroid-4-kky0upa4ye-16686@strange> (raw)
In-Reply-To:
Hi suppers,
sup 0.22.0 has been released:
== 0.22.0 / 2015-06-16
* Use mime-types 2
* Fix ruby style (Zeger-Jan van de Weg)
* Johannes Larsen: fix long-standing bug with draft-id mixups causing
drafts to disappear.
* Various bugs and minor improvements.
get it from rubygems:
$ gem install sup
or from:
$ git clone https://github.com/sup-heliotrope/sup
Thanks to all contributors!
Regards, Gaute
next reply other threads:[~2015-06-16 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 12:20 Gaute Hope [this message]
2015-06-18 8:42 ` Release 0.22.1 Gaute Hope
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=1434457165-astroid-4-kky0upa4ye-16686@strange \
--to=eg@gaute.vetsj.com \
--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