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.

I wonder if I can use the repo from both computers, without concurrency problems. 

I&#39;ve already tested, and on my end I can clone ok, but I&#39;m afraid of what might happen if we both access the same repo (push/pull), at the same time.

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&#39;m quite sure there isn&#39;t.

So, has anyone used a git repo on a network share, without a server, and without problems?

Thank you,&lt;br/&gt;
Alex

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.

&lt;b&gt;Update:&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;
My worries are not about the possibility of a network failure. Even so, we would have the required branches locally, and we&#39;ll be able to compile our sources.

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.

But, due to the fact we are doing this often, I am afraid about &lt;b&gt;file/repo corruption&lt;/b&gt;, if it happens that we both push/pull at the same time. Normally, we could &lt;i&gt;yell&lt;/i&gt; at each other each time we access the remote repo :), but it would be better to have it secured by the computers/network.

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&#39;t found anything conclusive yet.

&lt;b&gt;Update 2:&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;
The repo on the share drive would be a &lt;b&gt;bare&lt;/b&gt; repo, not containing a working copy.

All Network Share Solutions on Gang of Coders

Total of 1 Network Share Solutions

Concurrency in a GIT repo on a network shared folder