From: Loic Dachary <loic@dachary.org>
To: dillaman@redhat.com
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: rbd jewel backports related to mirroring
Date: Wed, 29 Jun 2016 15:04:03 +0200 [thread overview]
Message-ID: <5773C743.1090206@dachary.org> (raw)
In-Reply-To: <CA+aFP1Cp+Up4z7=JoNm+7PwtHXmFc2gfo+sYcEFMQ8pDLzwiLQ@mail.gmail.com>
Thanks for the hint, I'll try that.
On 29/06/2016 14:43, Jason Dillaman wrote:
> My usual strategy just involves running "git cherry-pick -x" against
> any prior commits associated with the file with the merge conflict (I
> usually try to pull in the whole PR instead of just the single commit
> causing the merge conflict). These extra cherry-picks will be cleanly
> merged away when the PRs are merged into a single branch. I usually
> run "git log --graph --decorate --date=relative --oneline" to see the
> associated PRs of prior commits.
>
> On Wed, Jun 29, 2016 at 5:07 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Jason,
>>
>> While working on jewel backports I noticed that there are a number of rbd backports ( http://tracker.ceph.com/projects/ceph/issues?per_page=100&query_id=96 ) related to mirroring. At least three of them do not apply cleanly and I suspect they are interdependant. Is there a way to figure out the order in which they should be applied ? If not I'll sort it out anyway, no worries ;-)
>>
>> Cheers
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>
>
>
--
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
prev parent reply other threads:[~2016-06-29 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 9:07 rbd jewel backports related to mirroring Loic Dachary
2016-06-29 12:43 ` Jason Dillaman
2016-06-29 13:04 ` Loic Dachary [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=5773C743.1090206@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@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 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.