qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Bruce Rogers <brogers@novell.com>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] move 'unsafe' to end of caching modes in help
Date: Tue, 27 Jul 2010 11:47:42 +0200	[thread overview]
Message-ID: <4C4EAB3E.6090306@redhat.com> (raw)
In-Reply-To: <m339v5pcmv.fsf@blackfin.pond.sub.org>

On 07/27/10 10:11, Markus Armbruster wrote:
> Anthony Liguori <anthony@codemonkey.ws> writes:
>> On 07/26/2010 02:19 PM, Avi Kivity wrote:
>>> We should try to support all users, prioritized by the number of end
>>> users they represent.  If this patch broke some other large user
>>> we'd be in a bind.  But likely this isn't the case so we aren't.
>>
>> As I've said, I'm pragmatic and that's why I've argued for these
>> changes in the past.  But libvirt should have changed a long time ago
>> to using something more reliable (like version).
> 
> You want pragmatic?  I can give you pragmatic!  We apply the trivial
> patch that helps libvirt and hurts nobody, and save our breath & typing
> for designing and implementing a capability system.

To be honest, this is exactly the same problem we had when the output
from -version changed and libvirt broke because it did static string
parsing instead of doing it properly. Back then the output of -version
was changed back to accommodate libvirt, but I am not aware that libvirt
went ahead and fixed the real problem in the mean time.

While I don't see this specific change being problematic, I don't like
the trend of hacking things to accommodate a specific library or
application, when the group relying on the feature really should start
providing the code for the real solution.

Just my $0.02

Jes

  reply	other threads:[~2010-07-27  9:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 20:32 [Qemu-devel] [PATCH] move 'unsafe' to end of caching modes in help Bruce Rogers
2010-07-21 20:55 ` Anthony Liguori
2010-07-21 21:32   ` Daniel P. Berrange
2010-07-21 21:45     ` Anthony Liguori
2010-07-21 21:58       ` Daniel P. Berrange
2010-07-21 23:39         ` Anthony Liguori
2010-07-22  0:45           ` Jamie Lokier
2010-07-22  6:53           ` Markus Armbruster
2010-07-22  8:42           ` Daniel P. Berrange
2010-07-22 14:19             ` Anthony Liguori
2010-07-23  8:00               ` Markus Armbruster
2010-07-26 15:53                 ` Anthony Liguori
2010-07-26 16:26                   ` Avi Kivity
2010-07-26 16:29                     ` Avi Kivity
2010-07-26 19:03                       ` Anthony Liguori
2010-07-26 19:24                         ` Avi Kivity
2010-07-26 19:43                           ` [Qemu-devel] " Juan Quintela
2010-07-26 16:40                     ` [Qemu-devel] " Anthony Liguori
2010-07-26 16:54                       ` Avi Kivity
2010-07-26 18:59                         ` Anthony Liguori
2010-07-26 19:19                           ` Avi Kivity
2010-07-26 19:35                             ` Anthony Liguori
2010-07-26 19:43                               ` Avi Kivity
2010-07-26 20:03                                 ` Anthony Liguori
2010-07-27  8:11                               ` Markus Armbruster
2010-07-27  9:47                                 ` Jes Sorensen [this message]
2010-07-27 12:30                                   ` Cole Robinson
2010-07-27 12:50                                     ` Anthony Liguori
2010-07-27 13:35                                       ` Cole Robinson
2010-07-27  8:26                               ` Markus Armbruster
2010-08-03  9:43                                 ` Richard W.M. Jones
2010-07-27  8:56                   ` Kevin Wolf
2010-07-22 13:45   ` Luiz Capitulino
2010-07-27 10:26 ` Daniel P. Berrange
2010-07-27 13:11   ` Bruce Rogers

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=4C4EAB3E.6090306@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=brogers@novell.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).