From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1kLc-0000nn-9e for qemu-devel@nongnu.org; Wed, 06 May 2009 12:51:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1kLW-0000hK-Vd for qemu-devel@nongnu.org; Wed, 06 May 2009 12:51:55 -0400 Received: from [199.232.76.173] (port=42105 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1kLW-0000hH-SW for qemu-devel@nongnu.org; Wed, 06 May 2009 12:51:50 -0400 Received: from yx-out-1718.google.com ([74.125.44.157]:61896) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M1kLW-0002OS-GH for qemu-devel@nongnu.org; Wed, 06 May 2009 12:51:50 -0400 Received: by yx-out-1718.google.com with SMTP id 6so105539yxn.82 for ; Wed, 06 May 2009 09:51:49 -0700 (PDT) Message-ID: <4A01C023.7060902@codemonkey.ws> Date: Wed, 06 May 2009 11:51:47 -0500 From: Anthony Liguori 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> <4A01A36D.7010704@redhat.com> In-Reply-To: <4A01A36D.7010704@redhat.com> 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: Avi Kivity Cc: Kevin Wolf , alex@csgraf.de, nolan@sigbus.net, qemu-devel@nongnu.org Avi Kivity wrote: > 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 URI escaping has some pretty strange rules because there set of characters allowed in a URI is << what is representable in a shell without requiring escaping. But honestly, I don't care that much. I'll leave the decision up to whoever writes up the patch. Regards, Anthony Liguori