From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Tue, 30 Nov 2010 08:22:48 +0200 [thread overview]
Message-ID: <1291097850-sup-6043@tilus.net> (raw)
In-Reply-To: <1291023322-sup-8457@meteor.durcheinandertal.local>
Gaudenz Steinlin, 2010-11-29 11:41:
> As far as I understood the branch layout the flow of changes is
> master -> next -> release. So applying to next would mean it ends up
> in the next release (0.12).
Master is considered "stable" and next "unstable". Releases are
tagged from master and small changes may go directly to master. New
features are introduced in next and merged to master when they are
considered stable (enough).
Applying to next would mean it ends up in 0.13 (or later if there are
bugfix releases).
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-11-30 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:08 Hamish D
2010-11-08 11:21 ` Hamish D
2010-11-08 22:32 ` Hamish D
2010-11-11 9:09 ` Gaudenz Steinlin
2010-11-11 17:25 ` Hamish D
2010-11-16 11:42 ` Gaudenz Steinlin
2010-11-16 14:20 ` Hamish D
2010-11-16 18:36 ` Gaudenz Steinlin
2010-11-16 23:05 ` Hamish D
2010-11-28 22:51 ` Hamish D
2010-11-29 9:41 ` Gaudenz Steinlin
2010-11-30 6:22 ` Tero Tilus [this message]
2010-12-01 8:37 ` Gaudenz Steinlin
2010-12-06 23:31 ` Hamish D
2010-12-23 18:43 ` Rich Lane
2011-01-19 3:11 ` Rich Lane
2011-01-30 23:57 ` Hamish D
2011-01-30 23:59 ` Hamish D
2011-01-19 16:12 ` Alvaro Herrera
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=1291097850-sup-6043@tilus.net \
--to=tero@tilus.net \
--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