Excerpts from B Smith-Mannschott's message of Tue Jan 12 13:29:41 -0500 2010: > How do you imagine that this would work in a distributed system such > as git? What would it mean to have the lock for "a file", when each > user effectively has their own branch? Hi Ben, Good question. I don't intend for the locking mechanism to leak into the distributed model of Git. It is solely for working copies, which /are/ centralized (just there can be a lot of them), when multiple people might be editing the same working copy. There is a somewhat natural question of: well, you should clone, make your changes in your own copy, and then push them back. That is arguably the correct mechanism. However, for casual users batonning changes from one repository to another is often more overhead than is really necessary, and I think a working copy locking mechanism will help for simple cases. Cheers, Edward -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html