From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56772 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Odfxb-0002on-6N for qemu-devel@nongnu.org; Tue, 27 Jul 2010 04:56:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Odfxa-0006P8-2V for qemu-devel@nongnu.org; Tue, 27 Jul 2010 04:56:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:8374) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OdfxZ-0006Os-QH for qemu-devel@nongnu.org; Tue, 27 Jul 2010 04:56:26 -0400 Message-ID: <4C4E9F35.7080007@redhat.com> Date: Tue, 27 Jul 2010 10:56:21 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] move 'unsafe' to end of caching modes in help References: <4C4704FC020000480009AB6E@sinclair.provo.novell.com> <4C475EC0.2000805@codemonkey.ws> <20100721213238.GB28871@redhat.com> <4C476A8A.6000707@codemonkey.ws> <20100721215833.GC28871@redhat.com> <4C478534.2020106@codemonkey.ws> <20100722084225.GA1524@redhat.com> <4C485383.8020904@codemonkey.ws> <4C4DAF94.1040300@codemonkey.ws> In-Reply-To: <4C4DAF94.1040300@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Bruce Rogers , Markus Armbruster , qemu-devel@nongnu.org Am 26.07.2010 17:53, schrieb Anthony Liguori: > I'm a practical guy, and I don't see that it's a huge burden for libvirt > to detect downstreams and build a feature matrix based on versions. If > someone demonstrates that it's infeasible, I'll happily reconsider. As a practical guy you should see that we're just about to make a release that doesn't work well with libvirt in this respect. Taking this patch won't fix the real problem, but it works around the implementation libvirt uses today and fixes the immediate problem. No doubt that libvirt needs to change their way of detecting features, but there's no way for them to release a new version which uses a different detection mechanism and which will be widespread by the 0.13 release (unless you plan to delay it another couple of months). We shouldn't start playing politics at the cost of our users. At least not in release versions. Kevin