[Top][All Lists]

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

Re: [Monotone-devel] Re: Re: Future of monotone

From: Markus Schiltknecht
Subject: Re: [Monotone-devel] Re: Re: Future of monotone
Date: Wed, 06 Feb 2008 09:57:00 +0100
User-agent: Mozilla-Thunderbird (X11/20080109)


Stephen Leake wrote:
I don't see how to do this on a branch basis.

The syntax of ~/.monotone/write-permission only allows specifying
users, not branches.

Correct, sorry for the noise, I mixed things up.

How do I specify that abe is allowed to upload branch "foo", but not
any other branch?

I can set get_revision_cert_trust to not trust things abe has
uploaded, but I don't see how to prevent the upload in the first

Yes, you can't currently prevent abe from uploading. But having the correct trust hook in place, you don't really need to. The problem is, every developer in your company will then need these trust hooks. This is (part of) the problem, policy branches should solve, IMO.

I'm currently thinking about if and how we can solve the trust problem in nuskool netsync. That's probably why I've confused things. Sorry again.



reply via email to

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