On Wed, Jan 05, 2011 at 04:42:49PM -0600, Neal Kreitzinger wrote: > In the case of concurrent pulls to the same non-bare repo, could the > working tree or index get corrupted, or does git have concurrency > control mechanisms for this too? There's a lock on the index, so it shouldn't be corruptable; one process will just end up waiting. I'm not sure offhand whether writing working tree files is done under any lock, but I would tend to think not, since it can be a long process. However, writing the same file twice should be OK; we unlink the old version and create the new from scratch. So the first writer will get its write-in-progress unlinked, and the second one will "win". -Peff -- 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