RFC: Managing Mercurial Repositories Remotely

[Peter Arrenbrecht]

On Wed, Feb 20, 2008 at 12:45 AM,  <Chuck.Kirschman at bentley.com> wrote:
> I agree with Peter that we'd prefer the remote .hg to copy.  We use
>  hooks for permission information, bug tracking, etc., and they will just
>  work based on the name and location of the repository if we copy the
>  .hgrc.  Just putting a clean repo up with hg init will not use our
>  server mechanisms correctly.  We could probably make it work if there is
>  a server-side hook called that knows the location of the new repository
>  so we can dig up the information, but it would be more convenient if it
>  just pulled it over.  Also, we host collections of repositories in
>  different subdirectories under the server.  So we either need to be able
>  to specify the subdirectory, or specify another repository in the
>  collection in order to put it in the right place.

Hmm. Maybe ensuring that the dirname of the clone is the same as the
dirname of the original plus not having /.hg/ in the path beyond
dirname(original) will suffice for security? Seems to me it would
ensure you cannot mess with hg's structures.

-peo