From: Alexandre Oliva <oliva@gnu.org>
To: David Zafman <dzafman@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] EC backfill retries
Date: Wed, 15 Mar 2017 17:13:52 -0300 [thread overview]
Message-ID: <ork27qguwv.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <06c85dc1-3318-fc05-ec1a-7f68d3aecc37@redhat.com> (David Zafman's message of "Fri, 10 Mar 2017 12:34:21 -0800")
On Mar 10, 2017, David Zafman <dzafman@redhat.com> wrote:
> I can't apply your patch because sha1 e3eb1fd isn't in the ceph
> repo
That's no surprise; that's the result of my cherry-picking the two
patches I listed as dependencies of mine.
> and it won't apply cleanly.
Do you have those two patches in the tree? (see the first quoted
paragraph below)
I recall one of them was already in jewel or jewel-next when I picked it
up, some time in December or so, but the other wasn't yet.
Anyway, if you do have the two deps, maybe I'll have to rebase. Just
let me know the target and I'll try to take care of it. I was targeting
the jewel branch, but I see I failed to make that explicit in my email.
Sorry about that.
> On 3/7/17 9:33 AM, Alexandre Oliva wrote:
>> Having applied David Zafman's patch for 13937 and Kefu Chai's for 17857,
>> I still hit the problem described in issue 18162. This mostly fixes it.
>> There are still remaining known problems:
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer
next prev parent reply other threads:[~2017-03-15 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 17:33 [PATCH 1/1] EC backfill retries Alexandre Oliva
2017-03-10 20:34 ` David Zafman
2017-03-15 20:13 ` Alexandre Oliva [this message]
2017-03-15 20:38 ` David Zafman
2017-03-16 17:44 ` Alexandre Oliva
2017-04-07 15:16 ` Alexandre Oliva
2017-04-07 17:15 ` David Zafman
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=ork27qguwv.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dzafman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox