From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix qemu-img argument handling
Date: Fri, 27 Feb 2009 13:08:37 -0600 [thread overview]
Message-ID: <49A83A35.8050706@us.ibm.com> (raw)
In-Reply-To: <498DB6D7.2090807@reactos.org>
Hervé Poussineau wrote:
> Hi,
>
> qemu-img doesn't work on MS Windows, when compiled with MinGW Runtime
> package >= 3.15
> According to
> http://sourceforge.net/tracker/index.php?func=detail&aid=2222263&group_id=2435&atid=102435
> , qemu-img shouldn't skip the first argument (command name) by doing
> optind++.
>
> Attached patch fixes the problems, and repairs qemu-img parsing with
> MinGW Runtime package >= 3.15
>
> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
This resend either inlining the patch or attaching it with text/plan.
Regards,
Anthony Liguori
> Hervé
prev parent reply other threads:[~2009-02-27 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 16:29 [Qemu-devel] [PATCH] Fix qemu-img argument handling Hervé Poussineau
2009-02-07 20:11 ` Robert Riebisch
2009-02-09 18:15 ` Aurelien Jarno
2009-02-14 17:33 ` Robert Riebisch
2009-02-27 19:08 ` Anthony Liguori [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=49A83A35.8050706@us.ibm.com \
--to=aliguori@us.ibm.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).