News for hackers. Stuff that matters.
Re:Git Large File Storage 1.0 by alkonaut on Thursday October 01, 2015 @05:15PM (#10314782)
Won't a central storage for the large files alao make it straightforward to add locking functionality in a future version of git-lfs, or as an add-in? I agree it sure looks like an omission to have a vcs that is centralized and aimed at binary data, without having any locking functionality.
Re:Git Large File Storage 1.0 by vvanders on Thursday October 01, 2015 @06:21PM (#10315190)
Yeah, but that's assuming a whole lot of infrastructure around marking files read-only.

I also haven't seen what the pull performance is like, P4 is a pretty known quantity(with caching as well).

Re:Git Large File Storage 1.0 by alkonaut on Friday October 02, 2015 @02:33AM (#10317039)
I don't even necessarily need my client to mark files as read only on my local machine. A system that just lets me query who has the lock on a certain file, and lets me get the lock on it if noone has, is miles ahead of shouting/email.

A remote-only locking system should be pretty easy to implement, e.g by just throwing in "filename.userid.lock" into the filesystem next to the file in question.

Re:Git Large File Storage 1.0 by sytse on Friday October 02, 2015 @03:43AM (#10317219)
We plan to add locking to the GitLab web ui at some point. At least this will prevent two people from locking the same file.