qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] configure: Add missing space when using --with-pkgversion
Date: Thu, 15 Feb 2018 08:11:51 -0600	[thread overview]
Message-ID: <5e448490-3a13-dd85-ded6-f9fa582d3901@redhat.com> (raw)
In-Reply-To: <20180215100812.GC3322@redhat.com>

On 02/15/2018 04:08 AM, Daniel P. Berrangé wrote:

>>> Hmm - here you're changing who supplies the ().  But that argues that
>>> maybe the callsites should supply " (" and ")" themselves.
>>
>> Yeah, that's likely the saner way to do this. The question is: What
>> about the query-version QMP command? Should it report parentheses or
>> not? I think I'd look nicer if it reports "package": "foo" instead of
>> "package": "(foo)" - but we maybe could break some users who expect
>> parentheses there (no matter whether there is a preceding space or not)?
> 
> The pkgversion is an opaque string - users/apps should never try to
> interpret its contents, because its format can vary arbitrarily between
> distros.  It is merely intended as an informative string to help the
> package maintainer identify which version of QEMU was used when someone
> submits a bug reoprt.
> 
> IOW it is totally valid to change the command to omit '()', and if anything
> breaks that is their own fault for trying to interpret an opaque blob of
> data.

Agreed - the fact that we had a leading space in the QMP output for a 
long time (and even inconsistent at whether it was there), with no one 
noticing, means that dropping the () from QMP won't hurt anyone.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

      reply	other threads:[~2018-02-15 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 17:31 [Qemu-devel] [PATCH] configure: Add missing space when using --with-pkgversion Thomas Huth
2018-02-14 18:33 ` Peter Maydell
2018-02-14 20:00   ` Thomas Huth
2018-02-14 20:15     ` Eric Blake
2018-02-14 20:23 ` Eric Blake
2018-02-15  6:02   ` Thomas Huth
2018-02-15 10:08     ` Daniel P. Berrangé
2018-02-15 14:11       ` Eric Blake [this message]

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=5e448490-3a13-dd85-ded6-f9fa582d3901@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    /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).