From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Steve Sistare <steven.sistare@oracle.com>,
Juan Quintela <quintela@trasno.org>,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>,
Avihai Horon <avihaih@nvidia.com>
Subject: Re: [PULL 00/26] Migration 20240104 patches
Date: Sun, 7 Jan 2024 07:41:25 -0500 [thread overview]
Message-ID: <CAJSP0QVA3USmat7EodQ7eBk+sf0FCT7oYBen_251ZMeeZHJ5dg@mail.gmail.com> (raw)
In-Reply-To: <ZZqaGf6nt0wkZgbS@x1n>
On Sun, 7 Jan 2024 at 07:34, Peter Xu <peterx@redhat.com> wrote:
>
> On Fri, Jan 05, 2024 at 04:08:40PM +0000, Peter Maydell wrote:
> > I notice that your gpg key doesn't seem to be signed by anybody
> > else; you might look at whether it's easy to get it signed
> > by somebody else (eg some of your redhat colleagues).
>
> Hmm, I think I have signed with at least Juan and Stefan. Which is the key
> server we normally use? Maybe I missed some steps there?
Yes, Peter's key is signed by me:
$ gpg --list-signatures 3B5FCCCDF3ABD706
pub ed25519/0x3B5FCCCDF3ABD706 2023-10-03 [SC]
Key fingerprint = B918 4DC2 0CC4 57DA CF7D D1A9 3B5F CCCD F3AB D706
uid [ full ] Peter Xu <xzpeter@gmail.com>
sig 3 0x3B5FCCCDF3ABD706 2023-10-03 [self-signature]
sig 0x9CA4ABB381AB73C8 2023-10-10 Stefan Hajnoczi
<stefanha@redhat.com>
uid [ full ] Peter Xu <peterx@redhat.com>
sig 3 0x3B5FCCCDF3ABD706 2023-10-03 [self-signature]
sig 0x9CA4ABB381AB73C8 2023-10-10 Stefan Hajnoczi
<stefanha@redhat.com>
sub cv25519/0xD5261EB1CB0C6E45 2023-10-03 [E]
sig 0x3B5FCCCDF3ABD706 2023-10-03 [self-signature]
I have pushed to the keyservers again in case I forget.
Stefan
next prev parent reply other threads:[~2024-01-07 12:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 4:31 [PULL 00/26] Migration 20240104 patches peterx
2024-01-04 4:31 ` [PULL 01/26] MAINTAINERS: Leaving Migration peterx
2024-01-04 4:31 ` [PULL 02/26] MAINTAINERS: Remove myself as reviewer from Live Migration peterx
2024-01-04 4:31 ` [PULL 03/26] cpus: vm_was_suspended peterx
2024-01-04 4:31 ` [PULL 04/26] cpus: stop vm in suspended runstate peterx
2024-01-04 4:31 ` [PULL 05/26] cpus: check running not RUN_STATE_RUNNING peterx
2024-01-04 4:31 ` [PULL 06/26] cpus: vm_resume peterx
2024-01-04 4:31 ` [PULL 07/26] migration: propagate suspended runstate peterx
2024-01-04 4:31 ` [PULL 08/26] migration: preserve " peterx
2024-01-04 4:31 ` [PULL 09/26] migration: preserve suspended for snapshot peterx
2024-01-04 4:31 ` [PULL 10/26] migration: preserve suspended for bg_migration peterx
2024-01-04 4:31 ` [PULL 11/26] tests/qtest: migration events peterx
2024-01-04 4:31 ` [PULL 12/26] tests/qtest: option to suspend during migration peterx
2024-01-04 4:31 ` [PULL 13/26] tests/qtest: precopy migration with suspend peterx
2024-01-04 4:31 ` [PULL 14/26] tests/qtest: postcopy " peterx
2024-01-04 4:32 ` [PULL 15/26] migration: Remove migrate_max_downtime() declaration peterx
2024-01-04 4:32 ` [PULL 16/26] migration: Remove nulling of hostname in migrate_init() peterx
2024-01-04 4:32 ` [PULL 17/26] migration: Refactor migration_incoming_setup() peterx
2024-01-04 4:32 ` [PULL 18/26] migration: Remove errp parameter in migration_fd_process_incoming() peterx
2024-01-04 4:32 ` [PULL 19/26] migration/multifd: Fix error message in multifd_recv_initial_packet() peterx
2024-01-04 4:32 ` [PULL 20/26] migration/multifd: Simplify multifd_channel_connect() if else statement peterx
2024-01-04 4:32 ` [PULL 21/26] migration/multifd: Fix leaking of Error in TLS error flow peterx
2024-01-04 4:32 ` [PULL 22/26] migration/multifd: Remove error_setg() in migration_ioc_process_incoming() peterx
2024-01-04 4:32 ` [PULL 23/26] migration: Fix migration_channel_read_peek() error path peterx
2024-01-04 4:32 ` [PULL 24/26] migration: Remove unnecessary usage of local Error peterx
2024-01-04 4:32 ` [PULL 25/26] migration/multifd: " peterx
2024-01-04 4:32 ` [PULL 26/26] migration: fix coverity migrate_mode finding peterx
2024-01-05 16:08 ` [PULL 00/26] Migration 20240104 patches Peter Maydell
2024-01-07 12:33 ` Peter Xu
2024-01-07 12:41 ` Stefan Hajnoczi [this message]
2024-01-07 15:23 ` Peter Maydell
2024-01-07 16:28 ` Stefan Hajnoczi
2024-01-08 2:10 ` Peter Xu
2024-01-08 2:34 ` Peter Xu
2024-01-08 15:22 ` Peter Maydell
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=CAJSP0QVA3USmat7EodQ7eBk+sf0FCT7oYBen_251ZMeeZHJ5dg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=avihaih@nvidia.com \
--cc=farosas@suse.de \
--cc=lsoaresp@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.org \
--cc=stefanha@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).