Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Gaute Hope <eg@gaute.vetsj.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Cc: Hamish D <dmishd@gmail.com>
Subject: Re: [sup-devel] sup 0.13
Date: Sun, 28 Apr 2013 22:54:23 +0200	[thread overview]
Message-ID: <517D8C7F.8050603@gaute.vetsj.com> (raw)
In-Reply-To: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>

On 28. april 2013 22:32, Hamish D wrote:
> I've also lost track of what's gone on to the develop branch. Should
> 0.13 be based on the master branch or develop?

develop should be ready for 0.13.

I don't know if it is useful; but I set up a few milestones in the tracker.


Cheers, Gaute


  reply	other threads:[~2013-04-28 20:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 20:32 Hamish D
2013-04-28 20:54 ` Gaute Hope [this message]
2013-04-29 11:02 ` Israel Herraiz
2013-04-29 11:39   ` Gaute Hope
2013-04-30  9:44     ` Horacio Sanson
2013-05-02  8:17       ` Gaute Hope
2013-05-09  1:39         ` Horacio Sanson
2013-05-20  7:24           ` Gaute Hope
2013-05-07 11:54 ` [sup-devel] sup 0.13 - please test Gaute Hope
2013-05-13  7:46   ` Gaute Hope
2013-05-13 23:15     ` Matthieu Rakotojaona

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=517D8C7F.8050603@gaute.vetsj.com \
    --to=eg@gaute.vetsj.com \
    --cc=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