From: Hanna Reitz <hreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/4] iotests/297: Cover tests/
Date: Wed, 1 Sep 2021 16:33:19 +0200 [thread overview]
Message-ID: <0fa5d384-23b6-c370-c124-490a1b200b5c@redhat.com> (raw)
In-Reply-To: <7260b639-c50b-c758-0e60-2e36acae35b0@virtuozzo.com>
On 01.09.21 15:34, Vladimir Sementsov-Ogievskiy wrote:
> A kind of ping:)
>
> Seems that never landed into master?
Yes, that’s true…
I was waiting for John (CC-ed) to send v3 of
https://lists.nongnu.org/archive/html/qemu-block/2021-07/msg00611.html,
because in
https://lists.nongnu.org/archive/html/qemu-block/2021-07/msg00611.html,
John was proposing to have it include these patches here.
But I guess there was no plan to change the patches (other than
correcting the comment in patch 3), so I suppose I might as well. (And
it seems like John has other things going on, so I don’t want to exert
pressure by waiting for a v3 with these patches O:))
But I think I do have to send v4, because of that comment. I suppose
there can be no harm in doing so. (And now I really wonder why I
haven’t done so all this time...)
Hanna
prev parent reply other threads:[~2021-09-01 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 15:43 [PATCH v3 0/4] iotests/297: Cover tests/ Max Reitz
2021-05-14 15:43 ` [PATCH v3 1/4] iotests/297: Drop 169 and 199 from the skip list Max Reitz
2021-05-14 15:43 ` [PATCH v3 2/4] migrate-bitmaps-postcopy-test: Fix pylint warnings Max Reitz
2021-05-14 15:43 ` [PATCH v3 3/4] migrate-bitmaps-test: " Max Reitz
2021-05-14 16:40 ` Vladimir Sementsov-Ogievskiy
2021-05-14 15:43 ` [PATCH v3 4/4] iotests/297: Cover tests/ Max Reitz
2021-09-01 13:34 ` [PATCH v3 0/4] " Vladimir Sementsov-Ogievskiy
2021-09-01 14:33 ` Hanna Reitz [this message]
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=0fa5d384-23b6-c370-c124-490a1b200b5c@redhat.com \
--to=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).