From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Anthony Liguori" <aliguori@us.ibm.com>,
patches@linaro.org, qemu-trivial@nongnu.org,
"John Rigby" <john.rigby@linaro.org>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line
Date: Mon, 20 May 2013 19:05:44 +0200 [thread overview]
Message-ID: <519A57E8.9090101@redhat.com> (raw)
In-Reply-To: <519A55F3.8090101@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 20/05/2013 18:57, Eric Blake ha scritto:
> Changing the name of an architecture would be reflected by having
> a different qemu-FOO binary name, right? If that's the case, then
> introspection of which architectures are supported is done by
> listing all the matches to qemu-* in the directory where binaries
> are installed, and we don't need a QMP enum duplicating what the
> file system already tells us.
Yes, that was exactly my point (plus, those binaries might well come
from different versions of QEMU).
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRmlfnAAoJEBvWZb6bTYbyDq0P/AkeSq6btQY4noFbY7WQwN3k
4+uDUjtwvobsuoqvEKYKMCo6MDyJnfNkgX7S6aNSj+v5+59/tlS0evjgj0N76FGj
GC2FcDmmqu3OSt9+2i+pU6gs3eSk6UFbZ9/nxI9hzJ5aaPq6vCr/0l/lR1Ru5op6
W6705VDwp13jhgx+P14OfwI3qLztIP6/mL8Mc58J+7Y+GQ2SCs1CPJgUH4EW76Qg
uSOZ6FuNan7Hv+aNdUBXeXRteT4AfzwiGeCi2Z5zxvztUJr9YsOx+TKD/6HbO+1l
mLyHsOAEba6Ic9N8t/kZLh8yMK44WMcTX7Xnc583NZOz/njBS3+wJqBQLaggj37N
FX0w0lYkcbflqIei9YKK5X2Pex8tOQxHB7NDoGgcXQiOtMC8s3CJ1J91PaPrEprm
m9s9PXtZ+AXO4gt1cH5sofdPY5NiIChQOjgmp4TFf90NG1+t0DLIqnJaA0BWKEBl
uQbdyV3jUyZOdF0hgGRhrt0S1MuOS2e+cCVj1/qNmoAFMkFKEKevInS3QxH2kSNs
wkjBHZ9g7LU8LO4qyBCpp4mxepsrKh9kgGnJDkx6cVULC3jkjbSqeORFYblgp/lm
4ZWc95r1m8XkLaIrxuA5DPO1yuHT/bfZiZp1KiwMRVD3vI877y31nUeSK8jdv3Rp
iVzfr9t7+uWYWRF3t516
=81Fx
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-05-20 17:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 16:21 [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-20 16:35 ` Paolo Bonzini
2013-05-20 16:38 ` Peter Maydell
2013-05-20 17:14 ` Paolo Bonzini
2013-05-22 13:15 ` Anthony Liguori
2013-05-22 13:50 ` Andreas Färber
2013-05-22 14:28 ` Anthony Liguori
2013-05-22 14:34 ` [Qemu-devel] New targets (was: [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line) Andreas Färber
2013-05-22 14:48 ` Anthony Liguori
2013-05-22 15:33 ` Peter Maydell
2013-05-22 16:10 ` Anthony Liguori
2013-05-22 13:51 ` [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-22 14:29 ` Anthony Liguori
2013-05-22 14:38 ` Paolo Bonzini
2013-05-24 21:38 ` [Qemu-devel] [libvirt] " Eric Blake
2013-05-25 9:18 ` Peter Maydell
2013-05-25 12:31 ` Andreas Färber
2013-05-20 16:41 ` [Qemu-devel] " Eric Blake
2013-05-20 16:47 ` Peter Maydell
2013-05-20 16:57 ` Eric Blake
2013-05-20 17:05 ` Paolo Bonzini [this message]
2013-05-22 13:12 ` Anthony Liguori
2013-05-22 13:38 ` Peter Maydell
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=519A57E8.9090101@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=john.rigby@linaro.org \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).