From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] Time for sup 0.13?
Date: Sat, 8 Oct 2011 16:15:28 +0100 [thread overview]
Message-ID: <CAOxvSbdWXmHQ78eDqE3Hq5L9m_xDBwpwA18vFdDtTTrig-QJ6Q@mail.gmail.com> (raw)
Hello all
I'm thinking it might be time to bundle up the last year of sup
development and push it out there. So if no one objects within a week
I'll merge next into master. I'll notify this list and sup-talk, and
give more people a chance to try it out and see if there are any
regressions. Assuming it's alright we should be able to make it sup
0.13 in November.
Of course William or Rich will need to push the gem out there as I
don't have access.
Hamish Downer
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-10-08 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 15:15 Hamish D [this message]
2011-10-08 16:49 ` 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=CAOxvSbdWXmHQ78eDqE3Hq5L9m_xDBwpwA18vFdDtTTrig-QJ6Q@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=sup-devel@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