qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [Qemu-devel] [PATCH] Fix double backslash problem in Windows
Date: Wed, 9 Jan 2008 10:51:36 +0100	[thread overview]
Message-ID: <fb249edb0801090151l4f43609di8e928418f449d394@mail.gmail.com> (raw)
In-Reply-To: <1199871092.4337.4.camel@frecb07144>

On 09/01/2008, Laurent Vivier <Laurent.Vivier@bull.net> wrote:
> Le mardi 08 janvier 2008 à 17:17 +0100, Hervé Poussineau a écrit :
> > Hi,
> >
> > On Windows, since December 2nd, files names provided in command line
> > have to double their backslash to work correctly, for example: "-hda
> > c:\\disks\\qemu.qcow" instead of -hda c:\disks\qemu.qcow"
> > This patch removes this need and reverts back to Qemu 0.9.0 behaviour
> >
> > Hervé
> >
>
> I have introduced this behavior to be able to use command line like
> "qemu -hda my\ file", IMHO your patch should be #ifdef for window only.

Why should qemu reimplement the escaping if shells already do that? If
parameter values with spaces are not handled correctly then it's an
error somewhere else.

I don't think there needs to be any difference in the handling of the
parameters between unix and ms-windows (in this case).
Regards

  reply	other threads:[~2008-01-09  9:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 16:17 [Qemu-devel] [PATCH] Fix double backslash problem in Windows Hervé Poussineau
2008-01-09  9:31 ` Laurent Vivier
2008-01-09  9:51   ` andrzej zaborowski [this message]
2008-01-09 10:04   ` Laurent Vivier
2008-01-09 10:40     ` andrzej zaborowski
2008-01-09 12:08       ` Laurent Vivier
2008-01-09 12:27         ` Johannes Schindelin
2008-01-09 12:51           ` Laurent Vivier
2008-01-09 13:27             ` Johannes Schindelin
2008-01-09 13:46               ` Laurent Vivier
2008-01-09 13:56                 ` andrzej zaborowski
2008-01-09 14:45                   ` Laurent Vivier
2008-01-09 13:59                 ` Johannes Schindelin
2008-01-09 14:42                   ` Laurent Vivier
2008-01-10  9:35               ` Laurent Vivier
2008-01-10 11:53                 ` Johannes Schindelin
2008-01-10 12:12                   ` Laurent Vivier
2008-01-10 12:15                     ` Johannes Schindelin
2008-01-10 12:33                       ` Laurent Vivier
2008-01-10 13:30                       ` Avi Kivity
2008-01-10 13:58                         ` Laurent Vivier
2008-01-10 14:18                           ` [Qemu-devel] " Jernej Simončič
2008-01-10 15:02                             ` Laurent Vivier
2008-01-10 18:13                               ` Laurent Vivier
2008-01-11  9:01                                 ` Laurent Vivier
2008-01-10 18:59                         ` [Qemu-devel] Re: [PATCH] " consul
2008-01-10 19:21                           ` Laurent Vivier
2008-01-09 12:27         ` [Qemu-devel] " Andreas Färber
2008-01-09 13:24           ` Laurent Vivier
2008-01-09 12:44         ` andrzej zaborowski
2008-01-09 17:53         ` Anthony Liguori
2008-01-09 18:23           ` Johannes Schindelin
2008-01-09 19:11           ` Laurent Vivier

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=fb249edb0801090151l4f43609di8e928418f449d394@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=hpoussin@reactos.org \
    --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).