Is there a check out lock in hg ?

[Kelly O'Hair]

Each person should have their own repository.

I'd never open up my repository for anyone to write to, they can
copy any of my working set files to their own repository if they
need my changed files before I commit them, but my repositories
should be treated as READ-ONLY (even if they aren't that way on the
file system).  And stay away from my toothbrush too... ;^)

Having more than one person work in a single Mercurial repository
doesn't make sense to me, just seems dangerous.

-kto

Thomas Arendsen Hein wrote:
> * T.J. Yang <tj_yang at hotmail.com> [20061215 12:28]:
>> I am  using RCS' "co -l fle" to serve as alert to avoid editing
>> same file by different persons at same time. Is there similar
>> mechanism in hg ?
> 
> No.
> 
> The usual way is to create a clone of the repository, edit, and then
> push back and (if necessary) merge.
> 
> 
> Maybe this can be implemented by an extension which marks files as
> read-only on update and provides a 'hg edit' command to create a
> user-writable version of the file. On commit or revert the file is
> made read-only again.
> 
> The other thing that has to be prevented in this case is another
> user updating or reverting the working directory, this can be done
> in the same extension, too, using hooks.
> 
> Anything else that needs to be locked?
> 
> Thomas
>