Breaking hard links between repositories

[Matt Cross]

Is there a clean way to break hardlinks between cloned repositories?

In our environment, we clone repositories on a central server, and
occasionally lock branches using file permissions to prevent accidental
pushes to a repository.  However, when a branch is cloned without a '--pull'
option, the data store files are hardlinked, and so permission changes
affect both repositories.  I know we can break the hardlinks by making a new
clone with the --pull option and switching to the new repository, but it
would be more convenient if there was a way to break the hardlinks in place
in an atomic manner (with respect to mercurial push/pull operations).

Thanks,
    -Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080520/2aa02a03/attachment.htm