From: Peter Xu <peterx@redhat.com>
To: Het Gala <het.gala@nutanix.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Prerna Saxena <prerna.saxena@nutanix.com>
Subject: Re: [PATCH 1/2] Fix typo to allow migrate_qmp_fail command with 'channels' argument
Date: Mon, 8 Apr 2024 14:56:48 -0400 [thread overview]
Message-ID: <CADLectnx5Hc9aXu9ADSf=f9Y6ZiXqjQ3UFxvt0Srifwvu1iudw@mail.gmail.com> (raw)
In-Reply-To: <76fa8f88-02e2-4431-bb28-5c29bbaa8436@nutanix.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Het,
It's all fine, no worries! This is good enough. Let's finish the
discussion in the next patch before a repost.
Thanks,
On Mon, Apr 8, 2024, 2:35 p.m. Het Gala <het.gala@nutanix.com> wrote:
>
> On 08/04/24 9:05 pm, Peter Xu wrote:
>
> !-------------------------------------------------------------------|
> CAUTION: External Email
>
> |-------------------------------------------------------------------!
>
> Hey, Het,
>
> On Sun, Apr 07, 2024 at 01:21:24PM +0000, Het Gala wrote:
>
> Fixes: (tests/qtest/migration: Add negative tests to validate migration QAPIs)
>
>
> I think I get your intention to provide two fixup patches on top of
> migration-next, which indeed would be preferred so that I can squash them
> into the patches before the pull.
>
> However please next time use "git commit --fixup" so that a better subject
> will be generated, and that'll make my life (and Fabiano's I suppose in the
> future) easier because git rebase understand those subjects. Then you
> don't need Fixes with an empty commit ID. They'll start with "fixup: XXX"
> pointing to a commit with subject rather than commit IDs.
>
> I apologize for any inconvenience caused by not using "git commit --fixup"
> in my previous submission. Let me resend the patchset with correct message
> convention. Will take care of this in future patches too, thanks for
> bringing it to my notice. Regards, Het Gala
>
[-- Attachment #2: Type: text/html, Size: 2486 bytes --]
next prev parent reply other threads:[~2024-04-08 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 13:21 [PATCH 0/2] Fix: qtest/migration: Improve multifd_tcp_channels_none test Het Gala
2024-04-07 13:21 ` [PATCH 1/2] Fix typo to allow migrate_qmp_fail command with 'channels' argument Het Gala
2024-04-08 15:35 ` Peter Xu
2024-04-08 18:35 ` Het Gala
2024-04-08 18:56 ` Peter Xu [this message]
2024-04-07 13:21 ` [PATCH 2/2] Call args->connect_channels to actually test multifd_tcp_channels_none qtest Het Gala
2024-04-08 15:40 ` Peter Xu
2024-04-08 19:27 ` 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='CADLectnx5Hc9aXu9ADSf=f9Y6ZiXqjQ3UFxvt0Srifwvu1iudw@mail.gmail.com' \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=het.gala@nutanix.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.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).