mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <>
To: Fredrik Gustafsson <>
Cc: "Peter Hüfner" <>,
	"" <>
Subject: Re: git on vagrant shared folder
Date: Tue, 14 Jul 2015 11:53:52 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

>> 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

  reply	other threads:[~2015-07-14 18:53 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 [this message]
2015-07-16  7:09     ` Peter Hüfner
2015-07-16 16:41     ` Junio C Hamano
2015-07-20  7:26       ` Peter Hüfner

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 \
    --in-reply-to='' \ \ \ \ \

* 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).