On Mon, 2007-07-30 at 11:46 -0700, Stephen Lau wrote:
> 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.
One issue with putting mercurial repositories in multi-user shared
writeable storage is the default handling of hgrc -- each person who
will be writing to the repository needs to make the owner of the hgrc
"trusted" in ~/.hgrc, and if you're using many different repositories
that will get unmanageable fast. (If you don't trust the repository's
hgrc, various hooks don't run and as a result it appears that policy
enforcement or other actions -- like mail notification -- won't happen).
- Bill
