From: "syeng" <syeng@yango.us>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Suggestions for Windows version of Qemu
Date: Thu, 5 Aug 2004 15:09:09 -0500 [thread overview]
Message-ID: <001101c47b28$26c353e0$3c389c3f@computername> (raw)
1) The source should be included, and optionally installed. Or at least
made available as a single package with whatever patches needed, etc. Both
the official release, and the daily builds on FreeOSZoo.
2) There should be a "whats new" or changelog or something included so we
can know what's new. Especially important for the daily builds.
3) The command line utils, such as qemu-img.exe, mkqemuimage.exe, etc.,
should prompt the user for the options, if there aren't any on the command
line. And there wont be when the user clicks on the program instead of
using a command line.
4) Instead of using a command line for everything, perhaps use a .INI file
for the settings? (Or perhaps.txt might be easier for people to edit.)
There are several public domain ini managers around and qemu probably
wouldn't need anything fancy anyway.
next reply other threads:[~2004-08-05 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 20:09 syeng [this message]
2004-08-05 21:03 ` [Qemu-devel] Re: Suggestions for Windows version of Qemu Ronald
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='001101c47b28$26c353e0$3c389c3f@computername' \
--to=syeng@yango.us \
--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).