Is there a check out lock in hg ?

John D. Mitchell jdmitchell at gmail.com
Sat Dec 16 00:08:00 UTC 2006


On 12/15/06, T.J. Yang <tj_yang at hotmail.com> wrote:
[...]
> >>I don't really know. All I know now this locking feature is very
> >>essential feature for rcs users to migrate over to hg.
> >
> >Why?  If they want to continue with a centralized, pessimistic-locking
> >based process why would they bother with a decentralized SCM system at
> >all?  There are plenty of centralized SCMs that support pessimistic
> >locking that are big improvements over rcs.
>
> Actually, I am using RCS as decentralized SCM. that is why I am
> interested about hg. Also I am using it for Unix system configuration file
> SCM not source code SCM. I shouldn't have said rcs users(implied all others), it
> should be just my case.

Anybody with any words of wisdom about using hg for system config
files?  I've been using hg only for source code so far.  The first
issue that comes to mind given my experiences is that hg doesn't yet
support symlinks.

> hg without file locking support will be just another cons I need to consider
> before I push for the change(switching from  RCS).

Sorry for being dense but that "requirement" still doesn't make any
sense to me.  If you're using a DSCM model then where is your need for
locking?

> Thanks for your response.
>
> I hope I am not consuming too much resources here with beginners' question.

No worries!  Always good to try and figure out different uses.

Take care,
John



More information about the Mercurial mailing list