Hi, I don't know if this helps you, but I found two strange things with your history that I want to point out. On Tue, Jul 14, 2015 at 05:49:43PM +0200, Peter Hüfner wrote: > The problem: > For development we are using virtual box controlled via vagrant with a shared folder on windows and mac hosts. The virtual OS ist ubuntu 14.04.2 LTS. In march this year we started with git in version around 2.3. With cloning a repo directly in the shared folder we haven’t had any problems. So you're running git on windows/os x and store the files on a shared folder on Ubuntu? This will have some strange side effects. Synchronization errors with the shared folder and the different file systems used might cause a problem (or might not). This is a unusual usecase and _very complex_ use case. I wouldn't be surprised if it breaks (git have had several bugs on shared folders before). My advise is to run git on the same machine as you store the git repo on. Git should not be runned over a network (no matter if the network is local on your computer or not). > A few weeks ago we weren’t able to clone and get an error: could not commit /vagrant/.git/config file. Manually we were able to change that file and also the clone command works outside the shared folder. Why are you trying to commit a file inside the .git dir? Files in that dir should not be commited (and I'm pretty sure there was a patch about this a while ago). The .git/config file for example is local to each git repo and should not be commited. -- Fredrik Gustafsson phone: +46 733-608274 e-mail: iveqy@xxxxxxxxx website: http://www.iveqy.com -- 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