From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: libvir-list@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string
Date: Wed, 8 Apr 2009 14:56:34 +0100 [thread overview]
Message-ID: <20090408135634.GA3841@shareable.org> (raw)
In-Reply-To: <200904072336.41097.paul@codesourcery.com>
Paul Brook wrote:
> I'm extremely sceptical of anything that claims to need a fine
> grained version number. In practice version numbers for open source
> projects are fairly arbitrary and meaningless because almost
> everyone has their own set of patches and backported fixes anyway.
I find it's needed onlyh when you need to interact with a program and
workaround bugs or temporarily broken features, and also when the
program gives no other way to determine its features. For some
reason, I find kernels are the main thing this matters for...
If the help text, some other output, or an API gives enough
information for interacting programs to know what to do, that's much
better and works with arbitrary patches etc.
-- Jamie
next prev parent reply other threads:[~2009-04-08 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:37 [Qemu-devel] Changing the QEMU svn VERSION string Anthony Liguori
2009-04-07 8:10 ` Gerd Hoffmann
[not found] ` <20090407090322.GC31447@redhat.com>
2009-04-07 13:52 ` [libvirt] " Anthony Liguori
2009-04-07 17:13 ` Jamie Lokier
2009-04-08 6:35 ` Gerd Hoffmann
2009-04-07 17:58 ` Daniel Jacobowitz
2009-04-07 22:36 ` Paul Brook
2009-04-08 13:13 ` Anthony Liguori
2009-04-08 13:56 ` Jamie Lokier [this message]
2009-04-07 9:04 ` [Qemu-devel] " Daniel P. Berrange
2009-04-07 16:09 ` [Qemu-devel] " Andreas Färber
2009-04-07 16:29 ` M. Warner Losh
2009-04-08 21:10 ` Andreas Färber
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=20090408135634.GA3841@shareable.org \
--to=jamie@shareable.org \
--cc=kraxel@redhat.com \
--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 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).