From: Loic Dachary <loic@dachary.org>
To: Matt Benjamin <mbenjamin@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: rgw backports
Date: Tue, 25 Oct 2016 11:52:42 +0200 [thread overview]
Message-ID: <580F2B6A.50509@dachary.org> (raw)
In-Reply-To: <1276006469.22059372.1477362126674.JavaMail.zimbra@redhat.com>
On 25/10/2016 04:22, Matt Benjamin wrote:
> Hi Loic,
>
> Sorry about the late response. Looks like you resolved the first two. Drilling into 3, does the lack of conditional -lldap obstruct automake build? Apparently not?
It looks like it's not a blocker indeed :-)
Cheers
> Regards,
>
> Matt
>
> ----- Original Message -----
>> From: "Loic Dachary" <loic@dachary.org>
>> To: "Matt Benjamin" <mbenjamin@redhat.com>
>> Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
>> Sent: Thursday, October 13, 2016 6:37:17 AM
>> Subject: rgw backports
>>
>> Hi Matt,
>>
>> The following jewel backports
>>
>> http://tracker.ceph.com/issues/17322
>> http://tracker.ceph.com/issues/17319
>> http://tracker.ceph.com/issues/17313
>>
>> conflict when trying to cherry-pick them and I would appreciate your advice
>> on how to handle them. Should they be resolved or do you think the best
>> action is to try to backport the commits that could prevent the conflict ?
>> If you don't have an opinion it's also fine, I'll figure it out ;-)
>>
>> Cheers
>> --
>> 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
>>
>
--
Loïc Dachary, Artisan Logiciel Libre
prev parent reply other threads:[~2016-10-25 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 10:37 rgw backports Loic Dachary
2016-10-25 2:22 ` Matt Benjamin
2016-10-25 9:52 ` 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=580F2B6A.50509@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=mbenjamin@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.