From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] rev3: support colon in filenames
Date: Fri, 17 Jul 2009 00:53:16 +0100
Message-ID: <200907170053.18816.paul@codesourcery.com>
References: <1245862739.6278.7.camel@localhost> <4A4CB39F.5070506@redhat.com> <20090715181405.GB3056@shareable.org>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Jamie Lokier <jamie@shareable.org>, Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>, linuxram@us.ibm.com,
	"kvm-devel" <kvm@vger.kernel.org>
To: qemu-devel@nongnu.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([65.74.133.4]:54895 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S933635AbZGPXxU (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 16 Jul 2009 19:53:20 -0400
In-Reply-To: <20090715181405.GB3056@shareable.org>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> So I propose this as a universal quoting scheme:
>
>     \<char> where <char> is not ASCII alphanumeric.

No thank you. This sounds dangerously like the windows command shell quoting 
rules. At first clance they appear to "just work", however when you actually 
try to figure out what's going on it gets horribly messy. For example UNC 
paths (which start with a double backslash) come out really weird with your 
suggestion.

Paul