monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Re: netsync connection info cleanup


From: Thomas Keller
Subject: Re: [Monotone-devel] Re: netsync connection info cleanup
Date: Wed, 28 Apr 2010 09:34:48 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.9) Gecko/20100317 SUSE/3.0.4-1.1.1 Lightning/1.0b2pre Thunderbird/3.0.4

Am 28.04.2010 02:00, schrieb Timothy Brownawell:
> On 04/27/2010 06:54 PM, Zack Weinberg wrote:
>> On Tue, Apr 27, 2010 at 4:42 PM, Timothy
>> Brownawell<address@hidden>  wrote:
>>>
>>> Is the occasional backslash really that bad? '%' conflicts with
>>> urlencoding
>>> (and '*' would only actually glob things if you have some really weirdly
>>> named files), and '?' is probably necessary for file/ssh sync.
>>
>> I think it's more important to avoid characters that are meaningful in
>> URLs (*especially* %) than to avoid characters that are meaningful to
>> the shell.  People expect to have to quote URLs.  Also, I don't like /
>> as a separator when it's not traversing a directory-like hierarchy.
> 
> Huh, hadn't really considered the "overloading '/'" aspect. It does seem
> slightly bad now that you mention it.
> 
>> So, how about this?
>>
>>   
>> protocol://address@hidden/path/to/database?include,include,-exclude,-exclude
>>
> 
> +1

+1/2 - this is similar to my last proposal (with ":" as separators, but
I'd accept "," as well) - but the mandatory "?" still strikes me. Do you
see any way to avoid "?" for the 90% use case (sync a single branch
without wildcards from / to a remote database)?

Thomas.

-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]