title: Concurrency in a GIT repo on a network shared folder
body: <p>I want to have a bare git repository stored on a (windows) network share. I use linux, and have the said network share mounted with CIFS. My coleague uses windows xp, and has the network share automounted (from ActiveDirectory, somehow) as a network drive.</p>
  
  <p>I wonder if I can use the repo from both computers, without concurrency problems. </p>
  
  <p>I've already tested, and on my end I can clone ok, but I'm afraid of what might happen if we both access the same repo (push/pull), at the same time.</p>
  
  <p>In the git FAQ there is a reference about using network file systems (and some problems with SMBFS), but I am not sure if there is any file locking done by the network/server/windows/linux - i'm quite sure there isn't.</p>
  
  <p>So, has anyone used a git repo on a network share, without a server, and without problems?</p>
  
  <p>Thank you,<br/>
  Alex</p>
  
  <p>PS: I want to avoid using an http server (or the git-daemon), because I do not have access to the server with the shares. Also, I know we can just push/pull from one to another, but we are required to have the code/repo on the share for back-up reasons.</p>
  
  <p><b>Update:</b><br /><br />
  My worries are not about the possibility of a network failure. Even so, we would have the required branches locally, and we'll be able to compile our sources.</p>
  
  <p>But, we usually commit quite often, and need to rebase/merge often. From my point of view, the best option would be to have a central repo on the share (so the backups are assured), and we would both clone from that one, and use it to rebase.</p>
  
  <p>But, due to the fact we are doing this often, I am afraid about <b>file/repo corruption</b>, if it happens that we both push/pull at the same time. Normally, we could <i>yell</i> at each other each time we access the remote repo :), but it would be better to have it secured by the computers/network.</p>
  
  <p>And, it is possible that GIT has an internal mechanism to do this (since someone can push to one of your repos, while you work on it), but I haven't found anything conclusive yet.</p>
  
  <p><b>Update 2:</b><br /><br />
  The repo on the share drive would be a <b>bare</b> repo, not containing a working copy.</p>