From: Mike Tremoulet <coffeemike@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Compiling QEMU in MSYS/MinGW (Win2K)
Date: Wed, 17 Nov 2004 15:29:28 -0600 [thread overview]
Message-ID: <5640213304111713297433c00@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0411172221440.25746@wgmdd8.biozentrum.uni-wuerzburg.de>
On Wed, 17 Nov 2004 22:22:26 +0100 (CET), Johannes Schindelin
<johannes.schindelin@gmx.de> wrote:
> It is known that since a couple of weeks you have to redirect the output
> of qemu in order to see it.
>
> Hth,
> Dscho
>
That's exactly what I was looking for. qemu.exe -h > test.txt
correctly output the information. Now I can go back to earlier
threads to find a fix.
Thanks,
-- Mike
prev parent reply other threads:[~2004-11-17 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 19:47 [Qemu-devel] Compiling QEMU in MSYS/MinGW (Win2K) Mike Tremoulet
2004-11-17 20:18 ` [Qemu-devel] " Ronald
2004-11-17 21:17 ` Mike Tremoulet
2004-11-17 21:19 ` Mike Tremoulet
2004-11-17 21:22 ` Johannes Schindelin
2004-11-17 21:29 ` Mike Tremoulet [this message]
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=5640213304111713297433c00@mail.gmail.com \
--to=coffeemike@gmail.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).