From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TwG7J-00029H-Gc for qemu-devel@nongnu.org; Fri, 18 Jan 2013 12:52:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TwFqE-00068X-71 for qemu-devel@nongnu.org; Fri, 18 Jan 2013 12:35:38 -0500 Received: from mx3-phx2.redhat.com ([209.132.183.24]:44057) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TwFqD-00068N-JS for qemu-devel@nongnu.org; Fri, 18 Jan 2013 12:34:57 -0500 Date: Fri, 18 Jan 2013 12:34:57 -0500 (EST) From: Paolo Bonzini Message-ID: <1217640499.8205475.1358530497031.JavaMail.root@redhat.com> In-Reply-To: <50F98084.4000200@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] define qemukvm-1.2 machine type List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cole Robinson Cc: Anthony Liguori , Marcelo Tosatti , qemu-devel@nongnu.org > > version_id and minimum_version_id should be changed to 2, as the > > comment indicates. > > But won't that mean we have to carry that patch forever, and while we carry > that patch we can never migrate from Fedora qemu to an upstream qemu instance? > I'd like to avoid carrying any incompatibility forward, if possible. To some extent you have to choose between backwards- and forwards- compatibility. But I think that you can achieve what you want by leaving version_id to 3, while setting minimum_version_id to 2. Paolo