From: Loic Dachary <loic@dachary.org>
To: "Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shiozawa, Kensuke" <shiozawa.kennsu@jp.fujitsu.com>,
"Nakao, Takanori" <nakao.takanori@jp.fujitsu.com>,
"Kawaguchi, Shotaro" <kawaguchi.s@jp.fujitsu.com>,
"Kaga, Yoshihiro" <y-kaga@jp.fujitsu.com>,
"Paul Von-Stamwitz (PVonStamwitz@us.fujitsu.com)"
<PVonStamwitz@us.fujitsu.com>
Subject: Re: mSHEC pull request (2nd challenge)
Date: Thu, 29 Jan 2015 15:37:39 +0100 [thread overview]
Message-ID: <54CA45B3.7030309@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AA68A90@g01jpexmbyt24>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Hi,
It looks good and ready for integration testing :-) I just created http://tracker.ceph.com/issues/10686 to track this feature. Since we are late in development cycle and unless someone has a different opinion, I will mark the SHEC plugin as experimental so people know it's new. I will however do that after it is merged in master.
Cheers
On 29/01/2015 15:24, Miyamae, Takeshi wrote:
> Hi Loic,
>
> When I reset our commits on our fork repository, the 1st pull request was automatically closed.
> So, I have issued another pull request of mSHEC.
>
> mSHEC : multiple Shingled Erasure Code #3534
> https://github.com/ceph/ceph/pull/3534
>
> As a result, I believe I have squashed our commits into one.
> I'm grad if you could restart the review.
>
> (You already noticed that and gave us labels, thank you!)
>
> Best regards,
> Takeshi Miyamae
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-01-29 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 14:24 mSHEC pull request (2nd challenge) Miyamae, Takeshi
2015-01-29 14:37 ` Loic Dachary [this message]
2015-01-30 10:28 ` Miyamae, Takeshi
2015-01-30 11:28 ` Loic Dachary
2015-01-30 13:04 ` Miyamae, Takeshi
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=54CA45B3.7030309@dachary.org \
--to=loic@dachary.org \
--cc=PVonStamwitz@us.fujitsu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=kawaguchi.s@jp.fujitsu.com \
--cc=miyamae.takeshi@jp.fujitsu.com \
--cc=nakao.takanori@jp.fujitsu.com \
--cc=shiozawa.kennsu@jp.fujitsu.com \
--cc=y-kaga@jp.fujitsu.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.