2 ms·
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 k
by vvanders 11y ago
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).
- alkonaut 11y agoI 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.
- sytse 11y agoWe plan to add locking to the GitLab web ui at some point. At least this will prevent two people from locking the same file.