From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1iRi-0005Nz-H8 for qemu-devel@nongnu.org; Wed, 06 May 2009 10:50:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1iRd-0005LO-VM for qemu-devel@nongnu.org; Wed, 06 May 2009 10:50:06 -0400 Received: from [199.232.76.173] (port=60951 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1iRd-0005LC-G4 for qemu-devel@nongnu.org; Wed, 06 May 2009 10:50:01 -0400 Received: from mx2.redhat.com ([66.187.237.31]:38822) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M1iRc-0000ax-Te for qemu-devel@nongnu.org; Wed, 06 May 2009 10:50:01 -0400 Message-ID: <4A01A36D.7010704@redhat.com> Date: Wed, 06 May 2009 17:49:17 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2 References: <1241571650-16212-1-git-send-email-alex@csgraf.de> <20090506082810.GB23167@redhat.com> <4A0154E9.7020705@redhat.com> <20090506093143.GC23167@redhat.com> <4A015F06.7050102@redhat.com> <4A018CD8.6000200@codemonkey.ws> <20090506133920.GK23167@redhat.com> <4A0195A3.7090205@redhat.com> <4A0197D9.9010109@codemonkey.ws> <4A019A87.7090505@redhat.com> <4A01A13F.6070001@codemonkey.ws> In-Reply-To: <4A01A13F.6070001@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , alex@csgraf.de, nolan@sigbus.net, qemu-devel@nongnu.org Anthony Liguori wrote: >> So what should the generic escaping look like? >> > > -drive file=my-silly\:filename\,with\ strange\ characters > > I see no reason to do anything overly complicated. Of course, if > you're in a shell, you'll have to double escape unless you've got > single quotes around it. That's a good argument for file: in addition > to escaping. > With backslash escaping, I never know how many backslashes I end up with. They're also the path separators in one OS. I'd go with URL separating: -drive file=file:my-silly%3afilename%2cwith%20strange%20characters -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.