From: James Pearson <pearson@changedmy.name>
Cc: sup-talk <sup-talk@rubyforge.org>,
Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] Release 0.13.1
Date: Fri, 21 Jun 2013 19:10:29 -0700 [thread overview]
Message-ID: <CA+ds9gJCfauTgS1LvrsOF0QREAKh9pKy=a550nj=1ZNi7wBvzA@mail.gmail.com> (raw)
In-Reply-To: <1371816327-sup-6968@qwerzila>
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
I was going to ask why the tags on the Gitorious repo[0] hadn't been
updated, when I visited the (new!) website and saw that development has
moved onto Github[1] (and restarted!). I'm apparently very behind the
times - and perhaps now I should dig out those changes I made and submit
them...
Glad to see things moving along again.
- P
[0]: http://gitorious.org/sup/mainline
[1]: https://github.com/sup-heliotrope/sup
On Fri, Jun 21, 2013 at 5:07 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> Greetings,
>
> I have just pushed version 0.13.1 of Sup to rubygems. This release holds
> should still be Ruby 1.8 compatible and holds the backported patches
> since the last release.
>
> No big changes, but a number of fixes has been applied.
>
> Regards, Gaute
>
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
[-- Attachment #1.2: Type: text/html, Size: 1567 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-06-22 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 12:07 Gaute Hope
2013-06-22 2:10 ` James Pearson [this message]
2013-06-22 10:48 ` [sup-talk] " Gaute Hope
2013-06-30 21:22 ` [sup-devel] " Hamish D
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='CA+ds9gJCfauTgS1LvrsOF0QREAKh9pKy=a550nj=1ZNi7wBvzA@mail.gmail.com' \
--to=pearson@changedmy.name \
--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