From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: laurent.vivier@bull.net
Cc: kvm-devel@lists.sourceforge.net,
"Jorge Lucángeli Obes" <t4m5yn@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Réf. : Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly executeadirectory (and storing command line options in it)
Date: Fri, 31 Aug 2007 22:09:13 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708312206120.28586@racer.site> (raw)
In-Reply-To: <OF5352114A.9C6CEEE4-ONC1257348.006F117A-C1257348.006F1248@frec.bull.fr>
Hi,
On Fri, 31 Aug 2007, laurent.vivier@bull.net wrote:
> I think passing only the directory name is better because it can be like
> a "black box" : the user don't have to know how it is inside.
I consider this a super downside.
"If you think your users are idiots, only idiots will use it [your
software]."
> And it is much more simple to use "qemu my_pc" than "qemu -c
> my_pc/config".
_Much_ more simple? Not really.
Having said that, it should not be a big problem to change the source just
for _you_, so that if "my_pc" could not be opened, it automatically tries
"my_pc/config". Trivial.
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-31 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 20:13 [Qemu-devel] Réf. : Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly executeadirectory (and storing command line options in it) laurent.vivier
2007-08-31 21:09 ` Johannes Schindelin [this message]
2007-09-01 14:22 ` [kvm-devel] [Qemu-devel] Réf. : " Avi Kivity
2007-09-01 22:59 ` Johannes Schindelin
2007-09-01 0:19 ` [Qemu-devel] Re: Réf. : Re: [kvm-devel] " Anthony Liguori
2007-09-01 5:44 ` Luke -Jr
2007-09-01 8:05 ` pterjan
2007-09-03 9:12 ` Laurent Vivier
2007-09-01 0:52 ` [Qemu-devel] Re: [kvm-devel] Réf. : " 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=Pine.LNX.4.64.0708312206120.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=laurent.vivier@bull.net \
--cc=qemu-devel@nongnu.org \
--cc=t4m5yn@gmail.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).