News for hackers. Stuff that matters.
Re:Kactus: Design version control without changing tools by slrz on Saturday February 24, 2018 @04:59PM (#16455674)
File locking basically being the antithesis to a distributed version control system, I can't really see how it would fit into Git. How would it work for a system with no central repository?

It might make more sense to implement this within the services that emulate a central repository on top of Git.

Re:Kactus: Design version control without changing tools by alkonaut on Saturday February 24, 2018 @06:17PM (#16456071)
You lock it in one central repository. There is typically a blessed repository somewhere, at least in every single project I have seen.

I know of no one and no project that uses the bare git in a truly distributed sense that isn’t just one central repo with multiple users, or in rare cases a hierarchy of repos such as the Linux kernel.

This is also why the github/lab style services are so popular - it’s what people need. But I don’t think that’s a reason to keep this feature away from git itself. I don’t think many want to have to use github just to get this one feature, and as I said, for any repo hosting binary content (common) and using one or more central blessed repos (nearly universal) - it’s very hard to live without.

Re:Kactus: Design version control without changing tools by davvid on Sunday February 25, 2018 @05:17PM (#16461518)
Gitolite has a fine implementation of locking in Git.

http://gitolite.com/gitolite/locking/#locking-binary-files

Locking is implemented centrally by gitolite. It would be nice if other services implemented the same mini-protocol.