Junio is absolutely right. I wasn’t trying to commit that file directly. The
error comes up when I want to change the config via git config or when I clone
the repo.
I also know that a shared folder is not a very friendly environment, but it is
the best solution for our situation here.
We recogn
Stefan Beller writes:
>>> 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
Hi Stefan, Hi Frederik,
maybe I stated the case not clearly enough.
The repo is just inside an shared/mounted folder from the VM to the Host, so
that we can access the sourcecode via an IDE running on the host. The git
commands are executed inside the VM on an ubuntu system. So there is no mix
>
>> 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
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 h
Dear git-Team,
we recognized a behavior that comes up with a newer git version. Unfortunately
we do not know which version exactly.
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. I
6 matches
Mail list logo
