Status of lfs and lock extensions

[Uwe Brauer]

>>> "DB" == Daniele Benegiamo <danielebenegiamo at fastwebnet.it> writes:

> Hi everyone,
> I would like to know if there are any news (or future plans) about the
> "lfs" extension and any sort of support for a "centralized file
> locking" feature.

> I know the subject is not an hot topic here, but most of our projects
> involve binary assets and we are often forced to switch to Subversion
> or working with less than ideal mixed solutions.

> The crucial missing feature for us is a "centralized file locking"
> feature (https://www.mercurial-scm.org/wiki/LockExtension). There's
> any known development on this area?


> Unfortunately all referenced extensions seems to gone lost after
> Bitbucket shut-down the hosted repositories. Anyone known of backups
> of such extensions? Or if they migrated the development elsewhere?

I think most are archived. I cloned the lock extension, it is outdated
and does not work with my current HG 5.2, since it is not maintained
there is little hope this will change. 

On the other hand, where do need it for? I thought of using it for my
hybrid solution: mercurial + dropbox, but for the moment it was
necessary. 

I also have the feeling that this extension is a bit against mercurial's
philosophy, but that should be judged better by others.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20210118/01028db3/attachment.p7s>