All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Filip Navara <filip.navara@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] [PATCH] Win32: Fix default prefix
Date: Sun, 02 Aug 2009 08:20:18 +0200	[thread overview]
Message-ID: <4A753022.1090404@mail.berlios.de> (raw)
In-Reply-To: <5b31733c0908011446s340709c0q6a416aefaf00f1b9@mail.gmail.com>

Filip Navara schrieb:
> On Sat, Aug 1, 2009 at 11:35 PM, Sebastian Herbszt<herbszt@gmx.de> wrote:
>   
>> Stefan Weil wrote:
>>     
>>> The old code resulted in wrong escape sequences:
>>>
>>> #define CONFIG_QEMU_SHAREDIR "c:\Program Files\Qemu"
>>>
>>> gcc warnings:
>>>
>>> vl.c:5708:20: warning: unknown escape sequence '\P'
>>> vl.c:5708:20: warning: unknown escape sequence '\Q'
>>>       
>> Looks like this got broken by "Generate config-host.h from config-host.mak"
>> (create_config).
>>
>>     
>>> Windows can handle slash (/) path separators,
>>> and QEMU already adds directories using slash,
>>> so there is no need to fight with the correct number
>>> of backslashes.
>>>       
>> Do all versions handle them correctly?
>>     
>
> At least all NT-based versions do and I believe Win 9x handles them
> correctly too.
>
> Best regards,
> Filip Navara
>
>   

Even IBM BIOS and all versions of MSDOS I know accept slash and backslash
in parameters for file system calls. So do all versions of Windows, too,

Regards
Stefan Weil

      reply	other threads:[~2009-08-02  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 19:30 [Qemu-devel] [PATCH] Win32: Fix default prefix Stefan Weil
2009-08-01 21:35 ` [Qemu-devel] " Sebastian Herbszt
2009-08-01 21:46   ` Filip Navara
2009-08-02  6:20     ` Stefan Weil [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=4A753022.1090404@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aliguori@us.ibm.com \
    --cc=filip.navara@gmail.com \
    --cc=herbszt@gmx.de \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.