From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
qemu-block@nongnu.org, libvir-list@redhat.com,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 0/1] dirty-bitmaps: remove deprecated autoload parameter
Date: Tue, 29 Oct 2019 15:02:20 +0100 [thread overview]
Message-ID: <2140d2fb-9c9d-d4cb-ec90-67062ed383d5@redhat.com> (raw)
In-Reply-To: <20190924230143.22551-1-jsnow@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
On 25.09.19 01:01, John Snow wrote:
> I'm going to be honest, here. There's actually no real reason to remove
> this now, but we could, so I'm going to.
>
> Also, in terms of the API serving as documentation, it's nicer to not
> pretend this is an option that does anything, so out it goes.
>
> This will serve as a little smoke test to see what happens if we
> actually stop dropping features we claimed were deprecated.
>
> John Snow (1):
> dirty-bitmaps: remove deprecated autoload parameter
>
> qemu-deprecated.texi | 20 +++++++++++++++-----
> qapi/block-core.json | 6 +-----
> blockdev.c | 6 ------
> 3 files changed, 16 insertions(+), 16 deletions(-)
Cleaning up my inbox... Was it your intention for someone other than
yourself to take this patch? :S
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-10-29 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 23:01 [PATCH 0/1] dirty-bitmaps: remove deprecated autoload parameter John Snow
2019-09-24 23:01 ` [PATCH 1/1] " John Snow
2019-09-25 1:35 ` Eric Blake
2019-09-25 7:20 ` Vladimir Sementsov-Ogievskiy
2019-09-25 13:01 ` John Snow
2019-09-25 13:43 ` Vladimir Sementsov-Ogievskiy
2019-10-29 14:02 ` Max 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=2140d2fb-9c9d-d4cb-ec90-67062ed383d5@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@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).