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 17:09:01 +0200 [thread overview]
Message-ID: <agNCjVL1sSICuAMa@redhat.com> (raw)
In-Reply-To: <20260512152402.0f18df61@penguin>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Am 12.05.2026 um 15:24 hat Lukas Straub geschrieben:
> On Tue, 12 May 2026 14:34:16 +0200
> Kevin Wolf <kwolf@redhat.com> wrote:
>
> > 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?
>
> I would prefer to review patches and you take them trough the block
> layer queue for now. The recent changes only have been drive-by/global
> refactorings anyway.
>
> I don't think I can send pull requests directly as my key is not yet
> signed for that.
The problem with the key should be solvable, but no problem, I can keep
taking things through the block tree.
> > Same question for this series, will you merge it yourself or would you
> > like someone else to pick it up?
>
> I would like someone else to pick it up.
I applied the series to my tree, give me a few more days for sending a
pull request.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-05-12 15:10 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
2026-05-12 13:24 ` Lukas Straub
2026-05-12 15:09 ` Kevin Wolf [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=agNCjVL1sSICuAMa@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 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.