QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Hanna Reitz <hreitz@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Peter Xu <peterx@redhat.com>, Zhang Chen <zhangckid@gmail.com>
Subject: Re: [PATCH 0/2] MAINTAINERS: Add myself as maintainer for replication
Date: Tue, 12 May 2026 14:34:16 +0200	[thread overview]
Message-ID: <agMeSMj8XETo1vMn@redhat.com> (raw)
In-Reply-To: <20260425-replication_maintainer-v1-0-f6ab019ff0ca@web.de>

Hi Lukas,

Am 25.04.2026 um 16:08 hat Lukas Straub geschrieben:
> I recently took up maintainership for the orphaned COLO migraion component.
> Here I take over maintainership for replication which is another important
> component for COLO.

What are your plans with replication? Will you be sending pull requests
directly to the global maintainer, or should we keep taking patches
through the block layer queues with your Acked-by?

Same question for this series, will you merge it yourself or would you
like someone else to pick it up?

> To: qemu-devel@nongnu.org
> Cc: qemu-block@nongnu.org
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: Hanna Reitz <hreitz@redhat.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Peter Xu <peterx@redhat.com>
> Cc: Zhang Chen <zhangckid@gmail.com>
> 
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> ---
> Lukas Straub (2):
>       MAINTAINERS: Add myself as maintainer for replication
>       MAINTAINERS: Rename Replication -> COLO block replication

Acked-by: Kevin Wolf <kwolf@redhat.com>



  parent reply	other threads:[~2026-05-12 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25 14:08 [PATCH 0/2] MAINTAINERS: Add myself as maintainer for replication Lukas Straub
2026-04-25 14:08 ` [PATCH 1/2] " Lukas Straub
2026-04-25 14:08 ` [PATCH 2/2] MAINTAINERS: Rename Replication -> COLO block replication Lukas Straub
2026-05-06 14:42 ` [PATCH 0/2] MAINTAINERS: Add myself as maintainer for replication Lukas Straub
2026-05-06 15:01   ` Peter Xu
2026-05-06 15:44   ` Zhang Chen
2026-05-12 12:34 ` Kevin Wolf [this message]
2026-05-12 13:24   ` Lukas Straub
2026-05-12 15:09     ` Kevin Wolf

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=agMeSMj8XETo1vMn@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=lukasstraub2@web.de \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhangckid@gmail.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