From: Peter Xu <peterx@redhat.com>
To: Het Gala <het.gala@nutanix.com>
Cc: qemu-devel@nongnu.org, marcandre.lureau@redhat.com,
thuth@redhat.com, lvivier@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v4 0/8] qtest: migration: Add tests for introducing 'channels' argument in migrate QAPIs
Date: Mon, 11 Mar 2024 17:38:49 -0400 [thread overview]
Message-ID: <Ze956ZixU-vaWPbM@x1n> (raw)
In-Reply-To: <66416dbd-9038-4762-b39a-9395b778ea56@nutanix.com>
On Tue, Mar 12, 2024 at 03:01:51AM +0530, Het Gala wrote:
>
> On 12/03/24 2:55 am, Peter Xu wrote:
> > On Sat, Mar 09, 2024 at 01:11:45PM +0530, Het Gala wrote:
> > > Can find the reference to the githab pipeline (before patchset) :
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_galahet_Qemu_-2D_pipelines_1207185095&d=DwIBaQ&c=s883GpUCOChKOHiocYtGcg&r=-qwZZzrw4EKSsq0BK7MBd3wW1WEpXmJeng3ZUT5uBCg&m=y2xUaOwvRVC5eTpFNEdxb37JYDdxN61W406HlCyx3CWIVyBRgLwjJhAYALZLinoi&s=vZRNX33_DuLO1TsfTpYR_s9bf_EMFm3oHHH_eg57zE0&e=
> > >
> > > Can find the reference to the githab pipeline (after patchset) :
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_galahet_Qemu_-2D_pipelines_1207183673&d=DwIBaQ&c=s883GpUCOChKOHiocYtGcg&r=-qwZZzrw4EKSsq0BK7MBd3wW1WEpXmJeng3ZUT5uBCg&m=y2xUaOwvRVC5eTpFNEdxb37JYDdxN61W406HlCyx3CWIVyBRgLwjJhAYALZLinoi&s=C73ka3k3ouAuRJYNVLPIBQiWx3jDFDDvVYDiEYqfE04&e=
> > Het,
> >
> > Please still copy me for any migration patches. In this case Fabiano is
> > looking it'll be all fine, but it will still help me on marking the emails.
> >
> > Thanks,
> So sorry about that Peter. I am aware that you and Fabiano are the go to
> migration
> maintainers. I thought I emailed or cc'd all the stakeholders that should be
> involved
> for this patchset series. Even in earlier series of this patchset, you were
> cc'ed,
> but somehow I just forgot to cc you for this patchset. Sure, will take care
> from next
> time. Again apologies for the mixup :)
No problem at all. As long as you have at least 1 maintainers copied,
logically nothing will get lost. It's just that it helps me in the routines.
Are you managing cc list manually for each version? In that case I suggest
you have a look at Stefan's tool:
https://github.com/stefanha/git-publish
It might help a great deal in patch managements at least to me, and it
definitely covers more than maintaining the cc list for a patchset.
--
Peter Xu
next prev parent reply other threads:[~2024-03-11 21:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 20:59 [PATCH v4 0/8] qtest: migration: Add tests for introducing 'channels' argument in migrate QAPIs Het Gala
2024-03-08 20:59 ` [PATCH v4 1/8] Add 'to' object into migrate_qmp() Het Gala
2024-03-08 20:59 ` [PATCH v4 2/8] Replace connect_uri and move migrate_get_socket_address inside migrate_qmp Het Gala
2024-03-11 18:16 ` Fabiano Rosas
2024-03-11 20:13 ` Het Gala
2024-03-08 20:59 ` [PATCH v4 3/8] Replace migrate_get_connect_uri inplace of migrate_get_socket_address Het Gala
2024-03-11 18:19 ` Fabiano Rosas
2024-03-11 20:33 ` Het Gala
2024-03-11 20:51 ` Fabiano Rosas
2024-03-11 20:57 ` Het Gala
2024-03-08 20:59 ` [PATCH v4 4/8] Add channels parameter in migrate_qmp_fail Het Gala
2024-03-11 18:20 ` Fabiano Rosas
2024-03-08 20:59 ` [PATCH v4 5/8] Add migrate_set_ports into migrate_qmp to update migration port value Het Gala
2024-03-11 18:42 ` Fabiano Rosas
2024-03-11 21:15 ` Het Gala
2024-03-08 20:59 ` [PATCH v4 6/8] Add channels parameter in migrate_qmp Het Gala
2024-03-11 18:44 ` Fabiano Rosas
2024-03-08 20:59 ` [PATCH v4 7/8] Add multifd_tcp_plain test using list of channels instead of uri Het Gala
2024-03-11 19:58 ` Fabiano Rosas
2024-03-08 20:59 ` [PATCH v4 8/8] Add negative tests to validate migration QAPIs Het Gala
2024-03-09 7:41 ` [PATCH v4 0/8] qtest: migration: Add tests for introducing 'channels' argument in migrate QAPIs Het Gala
2024-03-11 21:25 ` Peter Xu
2024-03-11 21:31 ` Het Gala
2024-03-11 21:38 ` Peter Xu [this message]
2024-03-11 21:59 ` Het Gala
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=Ze956ZixU-vaWPbM@x1n \
--to=peterx@redhat.com \
--cc=het.gala@nutanix.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).