From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Claudio Fontana <cfontana@suse.de>,
Steve Sistare <steven.sistare@oracle.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH V4 0/2] migration file URI
Date: Tue, 22 Aug 2023 15:25:37 +0200 [thread overview]
Message-ID: <1290963e-9f63-fc70-6729-d355d247c2fd@linaro.org> (raw)
In-Reply-To: <dba1e07d-6ebf-9329-7be7-4702ff5dc16d@suse.de>
Hi Claudio,
On 22/8/23 14:00, Claudio Fontana wrote:
> Hello,
>
> this series is all reviewed,
>
> and is needed as a precondition for further work to improve dramatically the performance of virsh save, virsh restore
> when migrating to disk, can it be merged?
$ ./scripts/get_maintainer.pl -f migration/meson.build
Juan Quintela <quintela@redhat.com> (maintainer:Migration)
Peter Xu <peterx@redhat.com> (reviewer:Migration)
Leonardo Bras <leobras@redhat.com> (reviewer:Migration)
qemu-devel@nongnu.org (open list:All patches CC here)
One maintainer, one single point of failure. When the
maintainer is busy or offline (vacations?) then everybody
is stuck.
This is usually solved by adding co-maintainers.
Juan, would you accept having co-maintainers helping you
dealing with the merge process? I'm not volunteering, but
this can be a good opportunity to make a formal request to
the community.
Regards,
Phil.
next prev parent reply other threads:[~2023-08-22 13:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:25 [PATCH V4 0/2] migration file URI Steve Sistare
2023-06-30 14:25 ` [PATCH V4 1/2] migration: " Steve Sistare
2023-08-30 13:16 ` Daniel P. Berrangé
2023-08-30 14:15 ` Steven Sistare
2023-09-08 10:52 ` Daniel P. Berrangé
2023-09-08 14:23 ` Steven Sistare
2023-06-30 14:25 ` [PATCH V4 2/2] migration: file URI offset Steve Sistare
2023-07-13 21:26 ` [PATCH V4 0/2] migration file URI Michael Galaxy
2023-08-22 12:00 ` Claudio Fontana
2023-08-22 13:25 ` Philippe Mathieu-Daudé [this message]
2023-08-30 13:09 ` Claudio Fontana
2023-09-13 13:00 ` Claudio Fontana
2023-09-27 13:14 ` migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI] Claudio Fontana
2023-09-27 13:56 ` Peter Xu
2023-09-27 14:36 ` Daniel P. Berrangé
2023-09-27 15:15 ` Peter Xu
2023-09-27 14:31 ` Daniel P. Berrangé
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=1290963e-9f63-fc70-6729-d355d247c2fd@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=steven.sistare@oracle.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;
as well as URLs for NNTP newsgroup(s).