From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Changing the QEMU svn VERSION string
Date: Mon, 06 Apr 2009 21:37:55 -0500
Message-ID: <49DABC83.7010608@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: libvir-list@redhat.com, kvm-devel <kvm@vger.kernel.org>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from rv-out-0506.google.com ([209.85.198.238]:40889 "EHLO
	rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751863AbZDGCiN (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 6 Apr 2009 22:38:13 -0400
Received: by rv-out-0506.google.com with SMTP id f9so2495816rvb.1
        for <kvm@vger.kernel.org>; Mon, 06 Apr 2009 19:38:10 -0700 (PDT)
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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, &micro, &kvm_version) != 4)
     kvm_version = 0;

if (!kvm_version && sscanf(help, "QEMU PC emulator version u.%u.%u",
     &major, &minor, &micro) != 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