From: Loic Dachary <loic@dachary.org>
To: Willem Jan Withagen <wjw@digiware.nl>, ceph-devel@vger.kernel.org
Subject: Re: Changing code in a subproject ceph-erasure-code-corpus
Date: Wed, 10 Feb 2016 18:31:15 +0700 [thread overview]
Message-ID: <56BB1F83.3090304@dachary.org> (raw)
In-Reply-To: <56BB1BFA.6040603@digiware.nl>
Hi,
You can submit a patch against https://github.com/ceph/ceph-erasure-code-corpus
Cheers
On 10/02/2016 18:16, Willem Jan Withagen wrote:
> Hi,
>
> I have one-line change in the erasure-code subproject.
> but git status reports:
> modified: ceph-erasure-code-corpus (modified content)
>
> So that change is not going to make it in my pull...
> But it is influencing my tests, and I keep fixing it after
> every fetch of the tree
>
> It is in
> ./ceph-erasure-code-corpus/v0.92-988/non-regression.sh:25
>
> and it replaces
> TMP=$(mktemp --directory)
> by
> TMP=$(mktemp -d)
>
> So how do get something like this commited?
>
> Thanx,
> --WjW
>
>
> --
> 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
next prev parent reply other threads:[~2016-02-10 11:31 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 [this message]
[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
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=56BB1F83.3090304@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=wjw@digiware.nl \
/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