From: Josh Durgin <jdurgin@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shu, Xinxin" <xinxin.shu@intel.com>
Subject: Re: rbd and the next firefly release v0.80.10
Date: Fri, 22 May 2015 14:08:58 -0700 [thread overview]
Message-ID: <555F9AEA.4080601@redhat.com> (raw)
In-Reply-To: <555F8B2D.30909@dachary.org>
On 05/22/2015 01:01 PM, Loic Dachary wrote:
> Hi Josh,
>
> The next firefly release as found at https://github.com/ceph/ceph/tree/firefly (68211f695941ee128eb9a7fd0d80b615c0ded6cf) passed the rbd suite (http://tracker.ceph.com/issues/11090#rbd). Do you think it is ready for QE to start their own round of testing ?
Looks good to me!
prev parent reply other threads:[~2015-05-22 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 20:01 rbd and the next firefly release v0.80.10 Loic Dachary
2015-05-22 21:08 ` Josh Durgin [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=555F9AEA.4080601@redhat.com \
--to=jdurgin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
--cc=xinxin.shu@intel.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.