From: Josh Durgin <jdurgin@redhat.com>
To: Jason Dillaman <dillaman@redhat.com>, Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RBD tests on the next dumpling release
Date: Mon, 09 Feb 2015 16:08:24 -0800 [thread overview]
Message-ID: <54D94BF8.7080008@redhat.com> (raw)
In-Reply-To: <1749420664.9284413.1423513637594.JavaMail.zimbra@redhat.com>
On 02/09/2015 12:27 PM, Jason Dillaman wrote:
> I would agree with your assessment that http://tracker.ceph.com/issues/10560#teuthology-runs-on-3944c77c404c4a05886fe8276d5d0dd7e4f20410-6-february sounds like a repeat of http://tracker.ceph.com/issues/4959.
>
> Josh, thoughts?
>
Yeah, that looks the same. I think we can ignore it.
next prev parent reply other threads:[~2015-02-10 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 22:30 RBD tests on the next dumpling release Loic Dachary
2015-02-06 14:05 ` Jason Dillaman
2015-02-06 14:17 ` Loic Dachary
2015-02-06 14:42 ` Jason Dillaman
2015-02-09 10:12 ` Loic Dachary
2015-02-09 20:27 ` Jason Dillaman
2015-02-10 0:08 ` Josh Durgin [this message]
2015-02-10 7:51 ` Loic Dachary
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=54D94BF8.7080008@redhat.com \
--to=jdurgin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=loic@dachary.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