From: Loic Dachary <loic@dachary.org>
To: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
Nathan Cutler <ncutler@suse.cz>,
Odintsov Vladislav <VlOdintsov@croc.ru>
Subject: Re: rgw and the next hammer release v0.94.6
Date: Fri, 5 Feb 2016 12:48:49 +0700 [thread overview]
Message-ID: <56B437C1.2020106@dachary.org> (raw)
In-Reply-To: <CADRKj5Qm-gQEnPsgYXjDxVrDUhQ8cOoXuuUJnPWRNm7MoF6d9g@mail.gmail.com>
On 05/02/2016 08:46, Yehuda Sadeh-Weinraub wrote:
> On Tue, Feb 2, 2016 at 8:45 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Yehuda,
>>
>> The next hammer release as found at https://github.com/ceph/ceph/tree/hammer passed the rgw suite (http://tracker.ceph.com/issues/13356#note-45). Do you think the hammer branch is ready for QE to start their own round of testing ?
>>
>
> Looks ok. There are also the two commits mentioned in this thread,
> which I'm fine with, but it's your call with regard to the timing.
I merged them. They have not been tested with a rgw suite but QE will run additional tests so the worst that can happen is that they fail there.
Thanks !
>
> Thanks,
> Yehuda
> --
> 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-05 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 4:45 rgw and the next hammer release v0.94.6 Loic Dachary
2016-02-04 6:40 ` Odintsov Vladislav
2016-02-05 1:46 ` Yehuda Sadeh-Weinraub
2016-02-05 5:48 ` 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=56B437C1.2020106@dachary.org \
--to=loic@dachary.org \
--cc=VlOdintsov@croc.ru \
--cc=ceph-devel@vger.kernel.org \
--cc=ncutler@suse.cz \
--cc=yehuda@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.