All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	"Paul Von-Stamwitz (PVonStamwitz@us.fujitsu.com)"
	<PVonStamwitz@us.fujitsu.com>,
	"Kaga, Yoshihiro" <y-kaga@jp.fujitsu.com>,
	"Kawaguchi, Shotaro" <kawaguchi.s@jp.fujitsu.com>
Subject: Re: mSHEC r33 release
Date: Sat, 24 Jan 2015 17:20:27 +0100	[thread overview]
Message-ID: <54C3C64B.4080804@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AA64EC2@g01jpexmbyt24>

[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]

Hi,

On 24/01/2015 10:09, Miyamae, Takeshi wrote:
> Hi Loic,
> 
> I have created a pull request of wip-mSHEC.
> 
> wip-mSHEC pull request #3484
> https://github.com/ceph/ceph/pull/3484
> 
> Besides, we changed the name of our fork repository.
> https://github.com/t-miyamae/wip-mSHEC
> 
> I'm not sure that it was done correctly because I am a beginner.
> Would you check it, please?

It looks like the branch from which you created the pull request still is master and not wip-mSHEC. That's not a problem. It only really becomes a problem if you have more than one pull request going on.

Cheers

> 
> Best regards,
> Takeshi Miyamae
> 
> -----Original Message-----
> From: Loic Dachary [mailto:loic@dachary.org] 
> Sent: Friday, January 23, 2015 11:40 PM
> To: Miyamae, Takeshi/宮前 剛
> Cc: Ceph Development; Shiozawa, Kensuke/塩沢 賢輔; Nakao, Takanori/中尾 鷹詔; Paul Von-Stamwitz (PVonStamwitz@us.fujitsu.com); Kaga, Yoshihiro/加賀 芳宏; Kawaguchi, Shotaro/川口 翔太朗
> Subject: Re: mSHEC r33 release
> 
> Thanks, I'll take a look. Could you please create a pull request against the master branch ? When you do so, it will be convenient if you submit from a branch that has a descriptive name such as wip-mSHEC or something similar.
> 
> Cheers
> 
> On 23/01/2015 15:30, Miyamae, Takeshi wrote:
>> Hi Loic,
>>
>> We have released mSHEC r33 just now.
>>
>> https://github.com/t-miyamae/ceph
>>
>> NOTABLE CHANGES
>>   - ensure thread safety
>>   - support generator matrix cache (added ErasureCodeShecTableCache.cc)
>>   - refer to the shared jerasure 2.0 library
>>   - improve verification of return code in test codes
>>   - add test code for verifying thread safety (added TestErasureCodeShec_thread.cc)
>>
>> LIMITATION
>>   - There are still lots of minor problems in test codes.
>>     We will fix it by 1/26(mon).
>>
>> Best regards,
>> Takeshi Miyamae
>>
> 
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-01-24 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 14:30 mSHEC r33 release Miyamae, Takeshi
2015-01-23 14:39 ` Loic Dachary
2015-01-24  9:09   ` Miyamae, Takeshi
2015-01-24 16:20     ` Loic Dachary [this message]
2015-01-26  2:21       ` Miyamae, Takeshi
2015-01-26  2:43         ` Miyamae, Takeshi
2015-01-23 20:51 ` Loic Dachary
2015-01-23 23:39 ` Loic Dachary
2015-01-24  8:13   ` Miyamae, Takeshi
2015-01-24 16:21     ` Loic Dachary
2015-01-23 23:59 ` 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=54C3C64B.4080804@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.