3 ms·
> Not sure I understand the problem. If I lock fileX and go to lunch, then I own the lock on that file while I’m out to lunch. And if you go on vacation for tw
by wyoung2 7y ago
> Not sure I understand the problem. If I lock fileX and go to lunch, then I own the lock on that file while I’m out to lunch.
And if you go on vacation for two weeks instead?
- alkonaut 7y agoSame thing obviously. But this is just a method of communication. It’s instead of emailing/shouting “don’t edit the background image today please” across the office. An admin can remove the lock. Or you can allow force-pushing by anyone to replace it or whatever. Not sure why this is seen as so complicated, version control systems have done it since forever. It’s not trying to solve some distributed lock system in a clever way. It’s dumb centralized mutex per file. And yet again this is all that’s needed (and it’s also added to git in git-LFS!).