From: Loic Dachary <loic@dachary.org>
To: Josh Durgin <jdurgin@redhat.com>,
Abhishek Varshney <abhishek.varshney@flipkart.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: rbd and the next infernalis release v9.2.1
Date: Thu, 11 Feb 2016 22:33:54 +0700 [thread overview]
Message-ID: <56BCA9E2.8000209@dachary.org> (raw)
In-Reply-To: <56BC2E43.5080206@redhat.com>
Merged !
On 11/02/2016 13:46, Josh Durgin wrote:
> On 02/10/2016 10:23 PM, Abhishek Varshney wrote:
>> Hi Josh,
>>
>> The next infernalis release as found at
>> https://github.com/ceph/ceph/tree/infernalis passed the rbd suite (
>> http://tracker.ceph.com/issues/13750#note-18 ). Do you think the
>> infernalis branch is ready for QE to start their own round of testing
>> ?
>
> I'd like to get the 4 in-flight changes in as well, since they've passed testing and just need commit message updates:
>
> https://github.com/ceph/ceph/pull/6981
> https://github.com/ceph/ceph/pull/7406
> https://github.com/ceph/ceph/pull/7484
>
> Jason, could you add the extra context to those commit messages?
>
> This last one looks ready as-is:
>
> https://github.com/ceph/ceph/pull/6629
>
> Josh
>
> --
> 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
--
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
prev parent reply other threads:[~2016-02-11 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 6:23 rbd and the next infernalis release v9.2.1 Abhishek Varshney
2016-02-11 6:46 ` Josh Durgin
2016-02-11 15:09 ` Jason Dillaman
2016-02-11 15:33 ` 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=56BCA9E2.8000209@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jdurgin@redhat.com \
/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.