CEPH filesystem development
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Changing code in a subproject ceph-erasure-code-corpus
Date: Thu, 11 Feb 2016 14:07:14 +0100	[thread overview]
Message-ID: <56BC8782.5010401@digiware.nl> (raw)
In-Reply-To: <56BB514A.10004@digiware.nl>

On 10-2-2016 16:03, Willem Jan Withagen wrote:
> On 10-2-2016 15:09, Loic Dachary wrote:
>> Once https://github.com/ceph/ceph/pull/7596 is merged, your change
>> will be in use. Would you mind verifying it's the case ?
>
> Thanx,
> And it'll show itself immediately on a next 'make check' run.
> IF it's not there, I'll let you know.

Hi Loic,

It has arived. Currently running a large recompile.

--WjW


>
> --WjW
>
>> On 10/02/2016 21:01, Loic Dachary wrote:
>>> Hi,
>>>
>>> On 10/02/2016 19:01, Willem Jan Withagen wrote:
>>>> On 10-2-2016 12:31, Loic Dachary wrote:
>>>>> Hi,
>>>>>
>>>>> You can submit a patch against
>>>>> https://github.com/ceph/ceph-erasure-code-corpus
>>>>
>>>> Right,
>>>>
>>>> Thru the github interface that went more than easy.....
>>>>
>>>> https://github.com/ceph/ceph-erasure-code-corpus/pull/3
>>>
>>> Merged, thanks !
>>>
>>
> --
> 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

      reply	other threads:[~2016-02-11 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 11:16 Changing code in a subproject ceph-erasure-code-corpus Willem Jan Withagen
2016-02-10 11:31 ` Loic Dachary
     [not found]   ` <56BB2696.30505@digiware.nl>
2016-02-10 14:01     ` Loic Dachary
2016-02-10 14:09       ` Loic Dachary
2016-02-10 15:03         ` Willem Jan Withagen
2016-02-11 13:07           ` Willem Jan Withagen [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=56BC8782.5010401@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    --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