All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mykola Golub <mgolub@mirantis.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: rbd backports
Date: Mon, 8 Aug 2016 22:30:07 +0300	[thread overview]
Message-ID: <20160808193006.GA2179@gmail.com> (raw)
In-Reply-To: <57A82FE4.10604@dachary.org>

Loic,

It works perfectly fine for me! Thank you for your detailed
explanation. Please, let me know if you need any other help with these
PRs from me.

On Mon, Aug 08, 2016 at 09:08:20AM +0200, Loic Dachary wrote:
> Hi Mykola,
> 
> A short note to explain why you were assigned a dozen rbd jewel backports today:
> 
> https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+assignee%3Atrociny+milestone%3Ajewel
> 
> Most of them were authored by someone from the backport team. They have been tested to not break the rbd suite so we are confident they do not contain a trivial problem. But our understanding of the rbd codebase is limited and before merging them we seek approval from the person who merged the original pull request in master. You merged a number of rbd pull request in master and this is why we end up asking for your final review on these backports.
> 
> Please let us know if this work is too much of a burden to you and we will try to find an alternate solution. Except for the simplest cases, figuring out if a set of commits makes sense in a stable version can be challenging.
> 
> 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

-- 
Mykola Golub

      reply	other threads:[~2016-08-08 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08  7:08 rbd backports Loic Dachary
2016-08-08 19:30 ` Mykola Golub [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=20160808193006.GA2179@gmail.com \
    --to=mgolub@mirantis.com \
    --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 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.