access control

[Steve Borho]

On Wed, 2007-08-29 at 21:42 +0400, Oleg Sukhodolsky wrote:
> Hi,
> 
> I'm trying to understand how I can control access to repository.
> Here are what I've found:
> 
> shared ssh (http://www.selenic.com/mercurial/wiki/index.cgi/SharedSSH)
> is for all or nothing access.
> Regular NFS/local uses regular file access permission, so you need to
> create special (Unix) groups for every project.
> 
> HTTP allows most flexible way to access control (allow_push, deny_push, etc)
> 
> Are these the only ways mercurial provides?  Or I have missed something?

There is also this:

http://www.selenic.com/mercurial/wiki/index.cgi/AclExtension

That said, you have much finer control over what gets included in your
main repository by using "pull" methods rather than "push" methods.

-- 
Steve Borho (steve at borho.org)
http://www.borho.org/~steve/steve.asc
Key fingerprint = 2D08 E7CF B624 624C DE1F  E2E4 B0C2 5292 F2C6 2C8C