From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39336 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OCZ4k-0000Tl-Dc
	for qemu-devel@nongnu.org; Thu, 13 May 2010 10:07:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <paul@codesourcery.com>) id 1OCZ4i-0003pA-Kx
	for qemu-devel@nongnu.org; Thu, 13 May 2010 10:07:46 -0400
Received: from mail.codesourcery.com ([38.113.113.100]:52347)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <paul@codesourcery.com>) id 1OCZ4i-0003ox-Cd
	for qemu-devel@nongnu.org; Thu, 13 May 2010 10:07:44 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Revive -version 'QEMU PC Emulator...'
Date: Thu, 13 May 2010 15:00:45 +0100
References: <1273696161-14332-1-git-send-email-crobinso@redhat.com>
	<4BEBF9A5.3070507@redhat.com> <20100513132102.GG12207@redhat.com>
In-Reply-To: <20100513132102.GG12207@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201005131500.45447.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

> > 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