From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lr1Cc-0006Cf-8W for qemu-devel@nongnu.org; Mon, 06 Apr 2009 22:38:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lr1CW-0006CT-Rl for qemu-devel@nongnu.org; Mon, 06 Apr 2009 22:38:16 -0400 Received: from [199.232.76.173] (port=58341 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lr1CW-0006CQ-Mk for qemu-devel@nongnu.org; Mon, 06 Apr 2009 22:38:12 -0400 Received: from rv-out-0708.google.com ([209.85.198.244]:26277) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lr1CW-0002wA-Bt for qemu-devel@nongnu.org; Mon, 06 Apr 2009 22:38:12 -0400 Received: by rv-out-0708.google.com with SMTP id k29so1710750rvb.2 for ; Mon, 06 Apr 2009 19:38:10 -0700 (PDT) Message-ID: <49DABC83.7010608@codemonkey.ws> Date: Mon, 06 Apr 2009 21:37:55 -0500 From: Anthony Liguori MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Changing the QEMU svn VERSION string Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" Cc: libvir-list@redhat.com, kvm-devel Hi, I'd like to update the VERSION string in QEMU's svn tree. Right now, it's 0.10.0 and since we have a 0.10.2 release, that's somewhat confusing. I don't want to make it 0.11.0 either because that's not going to be reliable from a feature detection perspective. What I would like is to make it 0.11.0-devel or something similar to that. Being the nice guy I am, I thought I would check that this didn't make libvirt go bonkers :-) This is the relevant detection code in libvirt: if (sscanf(help, "QEMU PC emulator version %u.%u.%u (kvm-%u)", &major, &minor, µ, &kvm_version) != 4) kvm_version = 0; if (!kvm_version && sscanf(help, "QEMU PC emulator version u.%u.%u", &major, &minor, µ) != 3) goto cleanup2; If I change SVN to 0.11.0-devel, that's going to break the KVM string although the QEMU string will continue to work. Avi could potentially carry a patch to keep it 0.10.x and since kvm-%u will be used to identify features, that should keep things working. Anyone have any objections/suggestions? Regards, Anthony Liguori