From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44658) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkcHh-0004VG-TR for qemu-devel@nongnu.org; Wed, 14 May 2014 12:44:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WkcHb-000235-Ju for qemu-devel@nongnu.org; Wed, 14 May 2014 12:44:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:27541) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkcHb-00022x-DO for qemu-devel@nongnu.org; Wed, 14 May 2014 12:43:55 -0400 Date: Wed, 14 May 2014 18:43:51 +0200 From: Kevin Wolf Message-ID: <20140514164351.GP3610@noname.redhat.com> References: <1399538540-5076-1-git-send-email-mbooth@redhat.com> <537276C6.5010308@redhat.com> <20140514074817.GB3610@noname.redhat.com> <5373951B.4080609@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P+33d92oIH25kiaB" Content-Disposition: inline In-Reply-To: <5373951B.4080609@redhat.com> Subject: Re: [Qemu-devel] Curl updates List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Matthew Booth Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org --P+33d92oIH25kiaB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 14.05.2014 um 18:08 hat Matthew Booth geschrieben: > On 14/05/14 03:48, Kevin Wolf wrote: > > Am 13.05.2014 um 21:47 hat Eric Blake geschrieben: > >> On 05/08/2014 02:42 AM, Matthew Booth wrote: > >>> [PATCH 1/4] curl: Fix parsing of readahead option from > >>> filename [PATCH 2/4] curl: Add sslverify option [PATCH 3/4] > >>> curl: Add usage documentation > >>>=20 > >>> The first 3 patches are reposted with updates following > >>> discussion of the option syntax. With this patch I've decided > >>> to break entirely with the previous syntax. Given that option > >>> parsing was previously both broken and undocumented, this is=20 > >>> hopefully a forgivable sin. > >>>=20 > >>> The new syntax is: > >>>=20 > >>> http://user:password@example.com/path?query[opt1=3Dval:opt2=3Dval] > >>>=20 > >>> I've bounded the option block in square brackets as these have > >>> no semantic meaning in any of the supported URI formats. > >>=20 > >> Offhand, I'm not liking this. Why not use a completely valid > >> URI, with '.../path?query&opt1=3Dval&opt2=3Dval'? Inventing your > >> own [opt1=3Dval:opt2=3Dval] on top of URI is asking for confusion. > >>=20 > >> Are you trying to support a way to pass a query string to the > >> curl URI, in addition to local options? How often do curl URIs > >> need a query? > >=20 > > My guess would be that you need this more often than local > > options. > >=20 > > Anyway, let's not add new options encoded in the URL, but point > > users to separate options. We may decide that we need the support > > the old crude way of encoding local options for compatibility, but > > preferably I would make filename just a plain URL. >=20 > Agree, but only when we support giving options to a backing file. Right, but we want that anyway. I applied Max's patches for the json: pseudo-protocol today, so we should have everything we need. Kevin --P+33d92oIH25kiaB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTc51HAAoJEH8JsnLIjy/WPUgP/2+T/q+cF3Ca+ZtiI75FS6m2 PvcL0TW1YeSPgXeyCaGfulH08rr8dTlQLiAT+fFdslHp1yrRGRG1ruCUCHR5Gu/g Vu0ATOGgZ0VRb07B6odicHmUq2U7d2EjR7VgTNRYjvtX3GMd7KsiU1SH/z2/geBw H+PsOyrUVfVnYx8Gne+oOiugKQESm3Y96I+WWRICe0VdUshqZr1i/qqvDhyF0tdA VgOwws4sbpBp8MkzmJq46rAm3RFhBB12F/pMn6ExPcQGxMe1AXxNXNgX1lkCDsph 2lG/+Az8OSaRRxgXdn80uNZ+i4LO5ivsquQrP2ShzLMvKwFdfGR5g4rDrog/Gzdj 4TEVYr4RvIFUO6RJssI9n52Lsxr/t/waGc4Uve6Z+iNv8ODNon8+fXUQB0qqMMv9 dkrycTWfEB964Z8o6dpZFmzBa8w+AFkYLGs21w03tvN61URUPDZGEixctrUC0Rwd AAmo8I7QbdBEkejhWjEZ+bVoyULIyZpTAB0SH46lrQvKSm0Hx7UL2mmO/Zh5f/oR 0w6fFnH/eRprAM/mN+aSPibBUMdBoiO0/Mju9Z2hjEiVUR+IIwgQOWZgDZvFWpDw D6s7FkWy40BvchdpjsYp/EUqEkHx/yu+klwfqObcsyo3/8yHQUWunIqiTOT5BVGz P6lzAGeJq37QJT8dNnOU =QtDH -----END PGP SIGNATURE----- --P+33d92oIH25kiaB--