Breaking hard links between repositories

[Matt Cross]

On Thu, May 22, 2008 at 5:04 PM, Guido Ostkamp <hg at ostkamp.fastmail.fm>
wrote:

> On Tue, 20 May 2008, Matt Cross wrote:
>
>  Is there a clean way to break hardlinks between cloned repositories?
>>
>>
> If I understand you correctly, you want to disable pushing from one repo
> clone to the original repo it was cloned from.
>
> This should be possible by simply renaming the directory of the original
> repo, e.g. from 'repo1' to 'repo1.locked'. An 'hg push' from the clone
> should then report something like
>
>  'abort: repository /home/testuser/hg-test/repo1 not found!'.
>
> The hardlinks and permissions on them should be unaffected by this method
> so anyone should still be able to read the files. As far as I know, as soon
> as someone needs to modify such a file by doing a commit in his clone,
> Mercurial will anyway break the hardlink itself in favor of a private copy
> stored in that repository.
>
>
That's a good idea, but we would like people to be able to clone and pull
from the repository while it is locked, but not be able to push into it.

Is there some file in the repository that will not be hard linked that we
can manage the permissions on to prevent pushing?

    -Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080527/248c972b/attachment.htm