All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: libvir-list@redhat.com, kvm-devel <kvm@vger.kernel.org>
Subject: Changing the QEMU svn VERSION string
Date: Mon, 06 Apr 2009 21:37:55 -0500	[thread overview]
Message-ID: <49DABC83.7010608@codemonkey.ws> (raw)

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

             reply	other threads:[~2009-04-07  2:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  2:37 Anthony Liguori [this message]
2009-04-07  8:10 ` [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string Gerd Hoffmann
2009-04-07  9:03   ` Daniel Veillard
2009-04-07 13:52     ` Anthony Liguori
2009-04-07 17:13       ` Jamie Lokier
2009-04-08  6:35         ` Gerd Hoffmann
2009-04-07 17:58       ` [libvirt] " Daniel Jacobowitz
2009-04-07 22:36         ` [libvirt] Re: [Qemu-devel] " Paul Brook
2009-04-08 13:13           ` Anthony Liguori
2009-04-08 13:56           ` Jamie Lokier
2009-04-07  9:04 ` Daniel P. Berrange

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=49DABC83.7010608@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.