mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Peter Hüfner" <>
To: Junio C Hamano <>
Cc: Stefan Beller <>,
	Fredrik Gustafsson <>,
	"" <>
Subject: Re: git on vagrant shared folder
Date: Mon, 20 Jul 2015 09:26:46 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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 recognized the error first time in the beginning of july, so the change done in june 30 seems to be a reason.
I will stay up to date and try it with newer git versions.

Mit freundlichen Grüßen
Peter Hüfner
e·confirm GmbH ..
Geschäftsführer: Roman Borch und Michael Posthoff
HRB 35653B   Steuernummer 37/211/10880
10119 Berlin Linienstr. 214
Tel.  +49 (0) 30 28 00 28 24 
Fax. +49 (0) 30 28 00 28 28

> Am 16.07.2015 um 18:41 schrieb Junio C Hamano <>:
> 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 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.
>> Actually it is considered a security risk, see
> I do not think Peter meant to "git add .git/config && git commit" by
> referring to the 'could not commit config file' error message he
> saw; you two are going in a wrong direction.
>    $ git grep 'could not commit'
>    config.c: error("could not commit config file %s", config_filename);
> I do share Fredrik's suspicion that the virtual filesystem the
> Ubuntu guest is trying to write to is at fault, but I never used
> "vagrant shared", and I do not know in what specific way their
> filesystem is not behaving as we expect.
> Applying 7a64592c (config.c: fix writing config files on Windows
> network shares, 2015-06-30) might be an interesting thing to try.
> Some filesystems do not want to rename a file that has mmaped region
> still active, which is my blind guess.

      reply	other threads:[~2015-07-20  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 15:49 git on vagrant shared folder Peter Hüfner
2015-07-14 18:32 ` Fredrik Gustafsson
2015-07-14 18:53   ` Stefan Beller
2015-07-16  7:09     ` Peter Hüfner
2015-07-16 16:41     ` Junio C Hamano
2015-07-20  7:26       ` Peter Hüfner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).