From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, devel@lists.libvirt.org,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH 2/4] qapi/migration: Deprecate migrate argument @detach
Date: Wed, 21 May 2025 16:28:33 +0200 [thread overview]
Message-ID: <87msb6yr5a.fsf@pond.sub.org> (raw)
In-Reply-To: <aC3VlBLa0nmaXNLW@x1.local> (Peter Xu's message of "Wed, 21 May 2025 09:31:00 -0400")
Peter Xu <peterx@redhat.com> writes:
> On Wed, May 21, 2025 at 08:37:09AM +0200, Markus Armbruster wrote:
>> Argument @detach has always been ignored. Start the clock to get rid
>> of it.
>>
>> Cc: Peter Xu <peterx@redhat.com>
>> Cc: Fabiano Rosas <farosas@suse.de>
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> docs/about/deprecated.rst | 5 +++++
>> qapi/migration.json | 18 +++++++++---------
>> 2 files changed, 14 insertions(+), 9 deletions(-)
>>
>> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
>> index 9665bc6fcf..ef4ea84e69 100644
>> --- a/docs/about/deprecated.rst
>> +++ b/docs/about/deprecated.rst
>> @@ -179,6 +179,11 @@ Use ``job-dismiss`` instead.
>>
>> Use ``job-finalize`` instead.
>>
>> +``migrate`` argument ``detach`` (since 10.1)
>> +''''''''''''''''''''''''''''''''''''''''''''
>> +
>> +This argument has always been ignored.
>> +
>> ``query-migrationthreads`` (since 9.2)
>> ''''''''''''''''''''''''''''''''''''''
>>
>> diff --git a/qapi/migration.json b/qapi/migration.json
>> index 8b9c53595c..ecd266f98e 100644
>> --- a/qapi/migration.json
>> +++ b/qapi/migration.json
>> @@ -1660,6 +1660,10 @@
>> #
>> # @resume: resume one paused migration, default "off". (since 3.0)
>> #
>> +# Features:
>> +#
>> +# @deprecated: Argument @detach is deprecated.
>> +#
>> # Since: 0.14
>> #
>> # .. admonition:: Notes
>> @@ -1668,19 +1672,14 @@
>> # migration's progress and final result (this information is
>> # provided by the 'status' member).
>> #
>> -# 2. All boolean arguments default to false.
>
> There's one more boolean ("resume") exists, but probably not a huge
> deal.. All booleans if not mentioned should have a default-false semantics
> at least to me.
Its default remains documented. It's visible above :)
> Reviewed-by: Peter Xu <peterx@redhat.com>
Thanks!
next prev parent reply other threads:[~2025-05-21 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 6:37 [PATCH 0/4] An overdue deprecation, a doc fix, a bit of cleanup Markus Armbruster
2025-05-21 6:37 ` [PATCH 1/4] docs/about: Belatedly document tightening of QMP device_add checking Markus Armbruster
2025-05-21 14:59 ` Stefan Hajnoczi
2025-05-27 15:01 ` Eric Blake
2025-05-28 4:51 ` Markus Armbruster
2025-05-21 6:37 ` [PATCH 2/4] qapi/migration: Deprecate migrate argument @detach Markus Armbruster
2025-05-21 7:46 ` Peter Krempa
2025-05-21 8:26 ` Peter Krempa
2025-05-21 9:21 ` Markus Armbruster
2025-05-21 12:47 ` Fabiano Rosas
2025-05-21 13:31 ` Peter Xu
2025-05-21 14:28 ` Markus Armbruster [this message]
2025-05-21 14:55 ` Peter Xu
2025-05-21 6:37 ` [PATCH 3/4] docs/about/deprecated: Move deprecation notes to tidy up order Markus Armbruster
2025-05-27 15:04 ` Eric Blake
2025-05-21 6:37 ` [PATCH 4/4] docs/about/removed-features: Move removal " Markus Armbruster
2025-05-27 15:05 ` Eric Blake
2025-05-27 7:45 ` [PATCH 0/4] An overdue deprecation, a doc fix, a bit of cleanup Markus Armbruster
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=87msb6yr5a.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.