From: Fabiano Rosas <farosas@suse.de>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: Re: [PATCH v2 3/3] migration/doc: We broke backwards compatibility
Date: Tue, 17 Oct 2023 13:56:25 -0300 [thread overview]
Message-ID: <87jzrlw5l2.fsf@suse.de> (raw)
In-Reply-To: <20231017151857.21328-4-quintela@redhat.com>
Juan Quintela <quintela@redhat.com> writes:
> When we detect that we have broken backwards compatibility in a
> released version, we can't do anything for that version. But once we
> fix that bug on the next released version, we can "mitigate" that
> problem when migrating to new versions to give a way out of that
> machine until it does a hard reboot.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Acked-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
prev parent reply other threads:[~2023-10-17 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 15:18 [PATCH v2 0/3] Migration Documentation for backward compatibility Juan Quintela
2023-10-17 15:18 ` [PATCH v2 1/3] migration/doc: Add documentation for backwards compatiblity Juan Quintela
2023-10-17 16:20 ` Peter Maydell
2023-10-18 11:24 ` Juan Quintela
2023-10-17 15:18 ` [PATCH v2 2/3] migration/doc: How to migrate when hosts have different features Juan Quintela
2023-10-17 16:50 ` Fabiano Rosas
2023-10-18 10:44 ` Juan Quintela
2023-10-17 15:18 ` [PATCH v2 3/3] migration/doc: We broke backwards compatibility Juan Quintela
2023-10-17 16:56 ` Fabiano Rosas [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=87jzrlw5l2.fsf@suse.de \
--to=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).