Khawaja Shams wrote: > I am still interested in knowing if git can handle multiple > simultaneous pushes on the same repository without encountering > corruption issues. Yes, concurrent attempts to update a branch are serialized. (But please don't ask me to answer about NFS semantics. See http://stackoverflow.com/questions/750765/concurrency-in-a-git-repo-on-a-network-shared-folder for some notes.) See the note about fast-fowards in the git push manual for how integrity is preserved. After reading that, you might wonder: if there are many, many clients pushing to the same branch, how is starvation avoided? Good question! It isn't. If you have so many clients wanting to push to a single branch, I would suggest having a single person or a few people maintaining it, pulling from others. Life will be better for many reasons, especially quality control. Hope that helps. Jonathan -- 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