From: Paolo Bonzini <pbonzini@redhat.com>
To: "Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Damien Hedde" <damien.hedde@greensocs.com>,
"Mark Burton" <mark.burton@greensocs.com>,
qemu-devel@nongnu.org,
"Mirela Grujic" <mirela.grujic@greensocs.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: Redesign of QEMU startup & initial configuration
Date: Mon, 13 Dec 2021 18:30:45 +0100 [thread overview]
Message-ID: <edbfff5c-65df-980c-acee-05055c254636@redhat.com> (raw)
In-Reply-To: <87ilvszg52.fsf@dusky.pond.sub.org>
On 12/13/21 16:19, Markus Armbruster wrote:
> I think it's more often just three: the long one that can do everything,
> the short one that can do simple things (and doesn't tell you anything
> about the long one), and the bad one you shouldn't use.
>
>> If we're going to have a good CLI, it would ideally only have
>> one way to do each given task.
> Ideally, the long one plus good defaults suffices.
That's hard to do, because the short one typically creates both a
backend and a frontend. It should be possible to macro-expand into the
long one + a -machine property, but that's extremely tedious work.
Paolo
> When we must also have a short one, it should macro-expand into long
> one(s), and the user should be able to see the expansion.
>
next prev parent reply other threads:[~2021-12-13 17:32 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 6:57 Redesign of QEMU startup & initial configuration Markus Armbruster
2021-12-09 19:11 ` Daniel P. Berrangé
2021-12-09 20:01 ` Mark Burton
2021-12-09 20:28 ` Daniel P. Berrangé
2021-12-10 8:34 ` Paolo Bonzini
2021-12-10 11:25 ` Daniel P. Berrangé
2021-12-10 14:15 ` Mark Burton
2021-12-10 14:26 ` Daniel P. Berrangé
2021-12-10 14:42 ` Mark Burton
2021-12-10 15:13 ` Paolo Bonzini
2021-12-10 15:26 ` Markus Armbruster
2021-12-10 15:39 ` Daniel P. Berrangé
2021-12-13 15:19 ` Markus Armbruster
2021-12-13 17:30 ` Paolo Bonzini [this message]
2021-12-13 17:59 ` Daniel P. Berrangé
2021-12-13 20:22 ` Mark Burton
2021-12-14 13:05 ` Daniel P. Berrangé
2021-12-14 13:11 ` Mark Burton
2021-12-14 13:21 ` Daniel P. Berrangé
2021-12-14 13:36 ` Mark Burton
2021-12-14 13:48 ` Daniel P. Berrangé
2021-12-14 14:42 ` Mark Burton
2021-12-14 14:56 ` Daniel P. Berrangé
2021-12-14 15:12 ` Markus Armbruster
2021-12-14 15:14 ` Mark Burton
2021-12-10 13:54 ` Markus Armbruster
2021-12-10 15:38 ` Paolo Bonzini
2021-12-13 15:28 ` Markus Armbruster
2021-12-13 17:37 ` Paolo Bonzini
2021-12-13 18:07 ` Daniel P. Berrangé
2021-12-13 18:37 ` Paolo Bonzini
2021-12-13 18:53 ` Daniel P. Berrangé
2021-12-14 7:09 ` Meeting today? Mark Burton
2021-12-14 11:37 ` Markus Armbruster
2021-12-14 11:39 ` Mark Burton
2021-12-14 12:49 ` Daniel P. Berrangé
2021-12-14 14:49 ` Markus Armbruster
2022-01-04 9:29 ` Edgar E. Iglesias
2022-01-06 11:21 ` "Startup" meeting (was Re: Meeting today?) Mark Burton
2022-01-06 11:23 ` Daniel P. Berrangé
2022-01-11 10:20 ` Philippe Mathieu-Daudé
2022-01-11 10:22 ` Mark Burton
2022-01-17 17:13 ` Kevin Wolf
2022-01-17 19:02 ` Markus Armbruster
2022-01-23 20:49 ` Mark Burton
2022-01-25 8:50 ` Juan Quintela
2022-01-25 10:45 ` Philippe Mathieu-Daudé via
2022-01-25 10:58 ` Juan Quintela
2022-02-08 11:52 ` Mark Burton
2022-02-08 12:35 ` Juan Quintela
2022-01-11 10:28 ` Daniel P. Berrangé
2021-12-15 18:46 ` Redesign of QEMU startup & initial configuration Paolo Bonzini
2021-12-15 18:50 ` Daniel P. Berrangé
2021-12-14 11:48 ` Markus Armbruster
2021-12-14 13:00 ` Mark Burton
2021-12-14 14:54 ` Markus Armbruster
2021-12-15 20:00 ` Paolo Bonzini
2021-12-15 20:14 ` Mark Burton
2021-12-16 10:24 ` Markus Armbruster
2021-12-16 15:28 ` Paolo Bonzini
2021-12-16 15:40 ` Daniel P. Berrangé
2021-12-16 16:00 ` Mark Burton
2021-12-16 16:15 ` Daniel P. Berrangé
2021-12-16 16:27 ` Mark Burton
2021-12-13 10:51 ` Damien Hedde
2021-12-13 15:47 ` Markus Armbruster
2022-01-04 12:40 ` Richard W.M. Jones
2022-01-13 16:10 ` Markus Armbruster
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=edbfff5c-65df-980c-acee-05055c254636@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=edgar.iglesias@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.burton@greensocs.com \
--cc=mirela.grujic@greensocs.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).