Richard Lowe wrote: > Stephen Lau <stevel at sun.com> writes: > > >> Mike Kupfer wrote: >> >>> [added scm-migration-dev to the cc list] >>> >>> >>>>>>>> "MikeC" == Shuai Mike Cheng <Mike.Cheng at Sun.COM> writes: >>>>>>>> >>> MikeC> In SWAN, what we can do over NFS it use the group id to let the >>> MikeC> people in the same project can do putback. But all of us are in >>> MikeC> the same group "staff". >>> >>> Yes, that's an interesting point. We've thought about how to do access >>> control for workspaces that live on opensolaris.org, but we haven't >>> thought much about access controls for other Mercurial workspaces. >>> >> I suppose we could advocate the use of ssh for other Hg workspaces as >> well, e.g.: >> ssh://onnv.eng/export/gate-hg/usr/closed >> >> It's not great though since you can't do things like: >> hg -R ssh://onnv.eng/export/gate-hg/usr/closed log >> which you can do for filesystem accessible repos. >> >> > > There's also the acl extension, delivered with Mercurial. > > -- Rich >
"The ACL extension lets you have fine grained access control to parts of a repository using deny and allow lists. "-- Description from http://www.selenic.com/mercurial/wiki/index.cgi/AclExtension I think acl extension is based on the basic HTTP or SSH access control and can't work independent. Just do a quickly test and looks my guess is correct. thanks Mike
