From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
qemu-block <qemu-block@nongnu.org>,
"Juan Quintela" <quintela@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v5 7/7] MAINTAINERS: Add myself as maintainer for yank feature
Date: Tue, 28 Jul 2020 12:41:46 +0100 [thread overview]
Message-ID: <20200728114146.GG3437398@redhat.com> (raw)
In-Reply-To: <c09e8bbd44783d9473e64994cad49da6fe2f8f74.1592923201.git.lukasstraub2@web.de>
On Tue, Jun 23, 2020 at 04:43:13PM +0200, Lukas Straub wrote:
> I'll maintain this for now as the colo usecase is the first user
> of this functionality.
>
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> ---
> MAINTAINERS | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 955cc8dd5c..a403d59190 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2506,6 +2506,19 @@ F: util/uuid.c
> F: include/qemu/uuid.h
> F: tests/test-uuid.c
>
> +Yank feature
> +M: Lukas Straub <lukasstraub2@web.de>
> +S: Odd fixes
> +F: util/yank.c
> +F: include/qemu/yank.h
For these 2 files,
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> +F: chardev/char-socket.c
> +F: block/nbd.c
> +F: migration/channel.c
> +F: migration/migration.c
> +F: migration/multifd.c
> +F: migration/qemu-file-channel.c
> +F: migration/savevm.c
You shouldn't be claiming maintainership of any of these
files.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-07-28 11:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:42 [PATCH v5 0/7] Introduce 'yank' oob qmp command to recover from hanging qemu Lukas Straub
2020-06-23 14:42 ` [PATCH v5 1/7] Introduce yank feature Lukas Straub
2020-07-28 11:34 ` Daniel P. Berrangé
2020-06-23 14:42 ` [PATCH v5 2/7] block/nbd.c: Add " Lukas Straub
2020-07-28 11:35 ` Daniel P. Berrangé
2020-06-23 14:42 ` [PATCH v5 3/7] chardev/char-socket.c: " Lukas Straub
2020-07-28 11:35 ` Daniel P. Berrangé
2020-06-23 14:42 ` [PATCH v5 4/7] migration: " Lukas Straub
2020-07-28 11:36 ` Daniel P. Berrangé
2020-06-23 14:42 ` [PATCH v5 5/7] io/channel-tls.c: make qio_channel_tls_shutdown thread-safe Lukas Straub
2020-07-28 11:39 ` Daniel P. Berrangé
2020-06-23 14:42 ` [PATCH v5 6/7] io: Document thread-safety of qio_channel_shutdown Lukas Straub
2020-07-28 11:39 ` Daniel P. Berrangé
2020-06-23 14:43 ` [PATCH v5 7/7] MAINTAINERS: Add myself as maintainer for yank feature Lukas Straub
2020-07-28 11:41 ` Daniel P. Berrangé [this message]
2020-06-24 19:47 ` [PATCH v5 0/7] Introduce 'yank' oob qmp command to recover from hanging qemu Lukas Straub
2020-07-05 9:35 ` Lukas Straub
2020-07-28 10:29 ` Stefan Hajnoczi
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=20200728114146.GG3437398@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=lukasstraub2@web.de \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).