File LOCK methods

[Martin Geisler]

"David Dyer-Bennet" <dd-b at dd-b.net> writes:

Hi David,

I've been designing a new lock extension and since it's quite useful
now, I searched the archive for questions about file locking. So this
thread came up where you asked:

> Following the advice here from last week, I'm looking into using hooks
> or something to coordinate allowing only one person to edit a file
> (the general use-case is complex text files maintained by GUI tools,
> which are very hard (and error-prone) to merge manually; the Windows
> RC file is our specific issue).
>
> This is intended to operate in a star topology, where everybody is
> working in repositories cloned off a central one. The really general
> case looked...intractable.

The extension works in exactly this situation: many clones that share
the same "lock repository". The communication is done over Mercurial's
normal channels (HTTP or SSH) and use their authentication.

If you're still interested, then please give it a spin and let us know
what you think:

  https://bitbucket.org/aragost/hglock/
  http://mercurial.selenic.com/wiki/LockExtension/NewDesign

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/