From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [Qemu-devel] [PATCH] rev3: support colon in filenames
Date: Wed, 15 Jul 2009 23:42:11 +0200
Message-ID: <4A5E4D33.9070901@web.de>
References: <4A434009.5010009@redhat.com> <1245998284.6278.99.camel@localhost> <4A447C8D.5000104@kevin-wolf.de> <1246063310.6278.115.camel@localhost> <1246511321.6429.31.camel@localhost> <4A4C754D.10109@redhat.com> <4A4CAD86.9020607@us.ibm.com> <4A4CB39F.5070506@redhat.com> <20090715181405.GB3056@shareable.org> <4A5E4206.20602@web.de> <20090715213635.GN3056@shareable.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig332FE510228D6431AEBE85E2"
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>, linuxram@us.ibm.com,
	qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
To: Jamie Lokier <jamie@shareable.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from fmmailgate01.web.de ([217.72.192.221]:38778 "EHLO
	fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754006AbZGOVmN (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 15 Jul 2009 17:42:13 -0400
In-Reply-To: <20090715213635.GN3056@shareable.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig332FE510228D6431AEBE85E2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Jamie Lokier wrote:
> Jan Kiszka wrote:
>>> Now, I see one significant hurdle with that: it's quite inconvenient
>>> for Windows users, typing paths like c:\path\to\dir\file, if those
>>> backslashes are stipped.
>> We could exclude Windows from this (I think to remember that filenames=

>> are more restricted there anyway) or define a different, Windows-only
>> escape character.
>=20
> I think both of those are bad ideas, because the same management
> scripts can run on Windows, and for consistency it's not just file
> names.  Even Windows has block devices and network devices :-)

I'm not sure if there is actually so much portability/reusability
between Windows and the rest of the universe, but I'm surely not an
expert in this.

>=20
> Fortunately "where <char> is not ASCII alphanumeric" solves the
> practical cases where the user types an ordinary pathname.
>=20
> Or the user can type forward slashes just like they do in unix.

We would still have to deal with the fact that so far '\' had no special
meaning on Windows - except that is was the well-known path separator.
So redefining its meaning would break a bit...

Jan



--------------enig332FE510228D6431AEBE85E2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkpeTTMACgkQniDOoMHTA+kAhACdF72TuJVSKU0f0F0GkVCLMhEB
/G8AnipLIDTFudqyCIBWdoSUIG8FzBm0
=yfO/
-----END PGP SIGNATURE-----

--------------enig332FE510228D6431AEBE85E2--