From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58100) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qoxig-0007i4-Ju for qemu-devel@nongnu.org; Thu, 04 Aug 2011 09:12:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qoxif-0000Mq-70 for qemu-devel@nongnu.org; Thu, 04 Aug 2011 09:12:14 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:43804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qoxif-0000Mm-4Z for qemu-devel@nongnu.org; Thu, 04 Aug 2011 09:12:13 -0400 Received: by ywb3 with SMTP id 3so1213930ywb.4 for ; Thu, 04 Aug 2011 06:12:12 -0700 (PDT) Message-ID: <4E3A9AA7.3010201@codemonkey.ws> Date: Thu, 04 Aug 2011 08:12:07 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1312326516-10117-1-git-send-email-aliguori@us.ibm.com> <4E389258.6040007@us.ibm.com> <4E398A44.8060507@codemonkey.ws> <4E3A97B5.6000002@redhat.com> In-Reply-To: <4E3A97B5.6000002@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Paolo Bonzini , Anthony Liguori , qemu-devel@nongnu.org, quintela@redhat.com On 08/04/2011 07:59 AM, Kevin Wolf wrote: > Am 03.08.2011 23:42, schrieb Juan Quintela: >> Anthony Liguori wrote: >>> On 08/03/2011 04:00 AM, Juan Quintela wrote: >> >>> I don't have a problem with Paolo's new protocol. In fact, I'm strong >>> in favor of applying it to master. But I don't like the idea of >>> adding a new migration protocol with no testing in master before >>> putting it in a release. >> >> I have. If we are changing a protocol in an incompatible version, we >> can remove a lot of warts that current descriptions have. Not that >> Paolo protocol is bad, but if we are going to do some change, adding >> things like size, removing previous warts, etc is the way to go. > > So how about stating clearly that migrating between 0.x and 1.x won't > work and using the next few months to develop a sane migration protocol? I'm all for it. Regards, Anthony Liguori > > We'll still have to do something about 0.15 and it's not very nice to > break migration twice, but seems there is no way around it. > > Kevin >