RFC: Managing Mercurial Repositories Remotely

[Jesse Glick]

Peter Arrenbrecht wrote:
> I think rinit should still reference an existing repo, if only to
> know which hgrc to link to

I must be missing something. Why do you need anything in the remote 
.hg/hgrc at all?

Copying hooks from an existing repo could be useful, though in a lot of 
such cases I would think you would need to edit the configuration 
anyway. For example, even if I wanted the notify extension to be used in 
a new clone, I would likely not want the same email mapping as the original.

> The reason I wanted to support mq on the server was for allowing easy
> web review of patches maintained in a queue.

Again I must be missing something. Why can't you just link to the actual 
patch (in the queue repository as browsable by hgwebdir)?

Regarding rinit, you could express this alternately as

$ hg rclone -r null $any-repo-at-all $new-repo