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 13:01:12 +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 08:42, schrieb address@hidden:
> On Tue, Apr 27, 2010 at 04:54:01PM -0700, Zack Weinberg wrote:
>> So, how about this?
>>
>>   
>> protocol://address@hidden/path/to/database?include,include,-exclude,-exclude
>>
>> should work equally well for mtn (with usher), ssh, and file.  Without
>> usher, you just leave out the /path part.
> 
> Does this mean that, with usher, it will now be mandatory to specify the 
> database explicitly?  That usher will no longer be able to make 
> decisions based on the branch name(s) involved?  And that, to a user,  
> usher-based monotones will look different from bare monotones?

No, this is merely an extension to usher (which iirc has already been
partially implemented by Tim) to have a third way to pick a database for
usher where DNS is not possible and branch pattern uniqueness might not
always be given.

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]