From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Time for sup 0.13?
Date: Sat, 08 Oct 2011 18:49:52 +0200 [thread overview]
Message-ID: <1318092478-sup-5464@qwerzila> (raw)
In-Reply-To: <CAOxvSbdWXmHQ78eDqE3Hq5L9m_xDBwpwA18vFdDtTTrig-QJ6Q@mail.gmail.com>
Excerpts from Hamish D's message of 2011-10-08 17:15:28 +0200:
> 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.
Yei! I favour.
- Gaute
prev parent reply other threads:[~2011-10-08 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 15:15 Hamish D
2011-10-08 16:49 ` Gaute Hope [this message]
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=1318092478-sup-5464@qwerzila \
--to=eg@gaute.vetsj.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