On 05/14/2014 03:20 PM, Matthew Booth wrote:
>
>> Right, but we want that anyway. I applied Max's patches for the
>> json: pseudo-protocol today, so we should have everything we need.
>
> I can't see this in block/master. Am I looking in the wrong place?
git://repo.or.cz/qemu/kevin.git block
o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/14 12:43, Kevin Wolf wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/14 13:02, Eric Blake wrote:
> On 05/14/2014 10:06 AM, Matthew Booth wrote:
>
The new syntax is:
http://user:passw...@example.com/path?query[opt1=val:opt2=val]
>
>>
>> A URI can, by definition, contain a query strin
On 05/14/2014 10:06 AM, Matthew Booth wrote:
>>> The new syntax is:
>>>
>>> http://user:passw...@example.com/path?query[opt1=val:opt2=val]
>>>
>
> A URI can, by definition, contain a query string, and we cannot assume
> that it won't. In fact, the use case I'm specifically interested in
> always
On 05/14/2014 10:08 AM, Matthew Booth wrote:
>> 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
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 ssl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 [PA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/05/14 15:47, Eric Blake wrote:
> 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
>>
>> The fi
On 05/14/2014 01:48 AM, Kevin Wolf wrote:
> 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.
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
> >
> > The first 3 patches are reposted wi
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
>
> The first 3 patches are reposted with updates following discussion of the
> option
> syntax. With
[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
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
12 matches
Mail list logo
