From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for October 11th
Date: Tue, 11 Oct 2011 15:47:47 +0200 [thread overview]
Message-ID: <4E944903.4020206@redhat.com> (raw)
In-Reply-To: <4E944440.1080109@codemonkey.ws>
On 10/11/2011 03:27 PM, Anthony Liguori wrote:
>> 5) Implement subsections through the wire as top-level sections (as
>> originally intended). Keep existing subsections with (1).
>
>
> That was (3).
>
Yes, sorry.
>> btw, it's reasonable to require that backwards migration is only to a
>> fully updated stable release, so we can do 5) too, or backport 1).
>
> But given the choice of a nasty silent failure to an
> not-quite-up-to-date stable release or failing migration to a fully
> up-to-date stable release, I think it's better that we err on the side
> of caution.
We're erring on the side of no migration, it seems.
> Not being able to migrate because of a recoverable failure is
> annoying. Having a silent failure that possible results in corruption
> is unacceptable.
What I'm trying to avoid is making choices today that close the door on
better fixes in the future.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-10-11 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 11:35 [Qemu-devel] KVM call agenda for October 11th Juan Quintela
2011-10-11 11:36 ` Paolo Bonzini
2011-10-11 12:54 ` Anthony Liguori
2011-10-11 11:48 ` Avi Kivity
2011-10-11 13:01 ` Anthony Liguori
2011-10-11 13:21 ` Avi Kivity
2011-10-11 13:27 ` Anthony Liguori
2011-10-11 13:47 ` Avi Kivity [this message]
2011-10-11 13:57 ` Anthony Liguori
2011-10-11 14:01 ` Avi Kivity
2011-10-11 14:34 ` Anthony Liguori
2011-10-11 14:43 ` Avi Kivity
2011-10-11 13:27 ` Juan Quintela
2011-10-11 13:54 ` Anthony Liguori
2011-10-11 15:39 ` Stefan Berger
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=4E944903.4020206@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--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).