From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@newdream.net>, ceph-devel@vger.kernel.org
Subject: Re: next branch is back
Date: Fri, 31 Oct 2014 23:01:04 +0100 [thread overview]
Message-ID: <545406A0.8040708@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1410311049060.27028@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
Hi,
I added the "next development release" to track pull requests targeting the next branch
https://github.com/ceph/ceph/labels
Feel free to remove / update if it is not a good idea.
Cheers
On 31/10/2014 18:49, Sage Weil wrote:
> The next branch is back. Please target bugfixes that should be in the
> next development release (v0.88) at next, and new code at master.
>
> Thanks!
> sage
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-10-31 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 17:49 next branch is back Sage Weil
2014-10-31 22:01 ` Loic Dachary [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=545406A0.8040708@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.