From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Jes.Sorensen@redhat.com, clalance@redhat.com,
qemu-devel@nongnu.org, crobinso@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH 1/1] Add -version-simple argument, printing only version number.
Date: Fri, 14 May 2010 15:06:25 +0100 [thread overview]
Message-ID: <20100514140625.GL9282@redhat.com> (raw)
In-Reply-To: <4BED4E73.2080802@linux.vnet.ibm.com>
On Fri, May 14, 2010 at 08:21:55AM -0500, Anthony Liguori wrote:
> On 05/13/2010 03:32 AM, Jes.Sorensen@redhat.com wrote:
> >From: Jes Sorensen<Jes.Sorensen@redhat.com>
> >
> >Add -version-simple argument for QEMU, printing just the version
> >number, without any supporting text.
> >
>
> I'm not a huge fan of the name.
>
> But what information are we trying to convey? Just major/minor number
> or would qemu-kvm also throw some info in there?
>
> Do version numbers even matter because 0.13 from qemu.git is going to be
> a hell of a lot different from 0.13 in RHEL6.x.
Version numbers are the last resort. We'll try all other avenues for
detecting a feature, before turning to a version number, precisely
because of the variance you mention here. When we do toggle something
based on a version though, we'll be conservative basing decision off
upstream QEMU 0.13 functionality, ignoring what extra bits a distro
might have backported (or even disabled).
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-05-14 14:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 8:32 [Qemu-devel] [PATCH] Add -version-simple argument to QEMU Jes.Sorensen
2010-05-13 8:32 ` [Qemu-devel] [PATCH 1/1] Add -version-simple argument, printing only version number Jes.Sorensen
2010-05-13 13:33 ` Daniel P. Berrange
2010-05-13 13:41 ` Jes Sorensen
2010-05-13 19:30 ` Blue Swirl
2010-05-14 9:42 ` Markus Armbruster
2010-05-14 10:06 ` Daniel P. Berrange
2010-05-14 11:24 ` Markus Armbruster
2010-05-14 13:34 ` Daniel P. Berrange
2010-05-14 13:48 ` Anthony Liguori
2010-05-14 13:57 ` Daniel P. Berrange
2010-05-14 13:27 ` Anthony Liguori
2010-05-14 13:32 ` Daniel P. Berrange
2010-05-14 14:25 ` Markus Armbruster
2010-05-14 13:21 ` [Qemu-devel] " Anthony Liguori
2010-05-14 13:58 ` Chris Lalancette
2010-05-14 14:06 ` Daniel P. Berrange [this message]
2010-05-17 6:54 ` Jes Sorensen
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=20100514140625.GL9282@redhat.com \
--to=berrange@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=clalance@redhat.com \
--cc=crobinso@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).