From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/2] Rework -boot option
Date: Mon, 20 Apr 2009 14:13:12 -0500 [thread overview]
Message-ID: <49ECC948.4040400@codemonkey.ws> (raw)
In-Reply-To: <49ECC01E.80605@web.de>
Jan Kiszka wrote:
> Everything is possible, but comes with a price:
> - more complex code
> - more ugly and inconsistent user interface
>
> Is there no precedence for breaking the command line interface in order
> to clean things up?
>
I'm not opposed to breaking syntax when necessary, but I think the
benefits need to be strong and every attempt at preserving compatibility
should be made.
If you really want a clean separation, introduce a different parameter
than -boot and make -boot deprecated.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-20 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 17:05 [Qemu-devel] [PATCH 1/2] Rework -boot option Jan Kiszka
2009-04-20 18:04 ` Anthony Liguori
2009-04-20 18:34 ` [Qemu-devel] " Jan Kiszka
2009-04-20 18:41 ` Avi Kivity
2009-04-20 20:01 ` [Qemu-devel] [PATCH 1/2 -v] " Jan Kiszka
2009-04-20 19:13 ` Anthony Liguori [this message]
2009-04-20 18:38 ` [Qemu-devel] [PATCH 1/2] " Daniel P. Berrange
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=49ECC948.4040400@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).