Is there a check out lock in hg ?

[T.J. Yang]

>From: Thomas Arendsen Hein <thomas at intevation.de>
>To: mercurial at selenic.com
>Subject: Re: Is there a check out lock in hg ?
>Date: Fri, 15 Dec 2006 18:46:28 +0100
>
>* 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.

Sounds great for this  extension but I don't know how to implement it.
Another other interests to see this got implemented ?

>
>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?

I don't really know. All I know now this locking feature is very
essential feature for rcs users to migrate over to hg.

Thanks for your reply

tj

>Thomas
>
>--
>Email: thomas at intevation.de
>http://intevation.de/~thomas/
>_______________________________________________
>Mercurial mailing list
>Mercurial at selenic.com
>http://selenic.com/mailman/listinfo/mercurial

_________________________________________________________________
View Athlete’s Collections with Live Search 
http://sportmaps.live.com/index.html?source=hmemailtaglinenov06&FORM=MGAC01