All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
	aliguori@us.ibm.com, clalance@redhat.com,
	Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Revive -version 'QEMU PC Emulator...'
Date: Thu, 13 May 2010 15:00:45 +0100	[thread overview]
Message-ID: <201005131500.45447.paul@codesourcery.com> (raw)
In-Reply-To: <20100513132102.GG12207@redhat.com>

> > But that is no different from what we have today. Users who update their
> > qemu and see issues with libvirt can also be asked to update libvirt. I
> > have already had several cases where I needed to do that anyway.
> 
> The general policy of QEMU has been to try and avoid  known breakage of
> existing apps unless unavoidable. This change introduced 100% guarenteed
> breakage of every single deployment that exists today, for the sake of
> removing 2 characters from a string. I really don't think this is a good
> cost/benefit tradeoff & agree with Cole that I'd like to see this reverted
> for the 0.13 release, and re-considered in a later release once we've had
> a chance to get a preventative fix out for libvirt using -version-string
> or equivalent.

For a stable release I'd agree, we shouldn't be breaking anything.
If combined with a version version bump I care a lot less.

Paul

  parent reply	other threads:[~2010-05-13 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 20:29 [Qemu-devel] [PATCH] Revive -version 'QEMU PC Emulator...' Cole Robinson
2010-05-12 20:38 ` [Qemu-devel] " Jes Sorensen
2010-05-12 20:48   ` Cole Robinson
2010-05-13  8:35     ` Jes Sorensen
2010-05-13 13:04       ` Cole Robinson
2010-05-13 13:07         ` Jes Sorensen
2010-05-13 13:21           ` Daniel P. Berrange
2010-05-13 13:38             ` Luiz Capitulino
2010-05-13 14:00             ` Paul Brook [this message]
2010-05-13 19:20               ` Blue Swirl
2010-05-13 21:24                 ` Stuart Brady
2010-05-14 13:24           ` Anthony Liguori
2010-05-14 13:54             ` Daniel P. Berrange
2010-05-14 14:22               ` Anthony Liguori
2010-05-14 14:42                 ` Daniel P. Berrange
2010-05-14 14:52                   ` Anthony Liguori
2010-05-14 15:02                     ` Daniel P. Berrange
2010-05-14 15:08                       ` Anthony Liguori
2010-05-14 13:17     ` Anthony Liguori
2010-05-14 13:25       ` 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=201005131500.45447.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=berrange@redhat.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 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.