From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: "gitster@pobox.com" <gitster@pobox.com>,
"pclouds@gmail.com" <pclouds@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Unable to create temporary file '/var/git/tmv3-target-overlay.git/shallow_Un8ZOR': Permission denied
Date: Mon, 21 Sep 2015 17:08:49 +0000 [thread overview]
Message-ID: <1442855328.29498.30.camel@transmode.se> (raw)
In-Reply-To: <xmqqpp1bbtvz.fsf@gitster.mtv.corp.google.com>
On Mon, 2015-09-21 at 09:48 -0700, Junio C Hamano wrote:
> Duy Nguyen <pclouds@gmail.com> writes:
>
> > Is it really necessary to remove write access in $GIT_DIR? Do we (git
> > devs) have some guidelines about things in $GIT_DIR?
>
> Those who are allowed to "git push" into it should be able to write
> there. It is a different matter that "git" program itself may make
> a policy decision to disallow some operations that the filesystem
> bits alone would have allowed (e.g. you can arrange the "pusher" to
> only come over the wire via "receive-pack" and "receive-pack" may
> deliberately lack support for writing into $GIT_DIR/config).
>
I view $GIT_DIR similar to "/" and "/tmp". Normally one does not let normal users write to "/"
as you want to keep this level clean. It is not obvious to everybody what files are important
under $GIT_DIR when mixed with tmp files etc.
$GIT_DIR/tmp would solve this nicely.
Jocke
next prev parent reply other threads:[~2015-09-21 17:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 11:36 Unable to create temporary file '/var/git/tmv3-target-overlay.git/shallow_Un8ZOR': Permission denied Joakim Tjernlund
2015-08-21 11:50 ` Joakim Tjernlund
2015-08-31 9:03 ` Joakim Tjernlund
2015-08-31 9:56 ` Duy Nguyen
2015-09-14 15:37 ` Joakim Tjernlund
2015-09-17 13:18 ` Duy Nguyen
2015-09-17 16:54 ` Joakim Tjernlund
2015-09-19 2:21 ` Duy Nguyen
2015-09-19 2:26 ` Duy Nguyen
2015-09-19 7:13 ` Johannes Schindelin
2015-09-20 13:36 ` Joakim Tjernlund
2015-09-19 8:44 ` Joakim Tjernlund
2015-09-21 16:48 ` Junio C Hamano
2015-09-21 17:08 ` Joakim Tjernlund [this message]
2015-09-22 20:00 ` Johannes Schindelin
2015-09-22 20:58 ` Joakim Tjernlund
2015-09-23 11:10 ` Johannes Schindelin
2015-09-23 15:13 ` Junio C Hamano
2015-09-23 20:41 ` Joakim Tjernlund
2015-09-23 22:48 ` Johannes Schindelin
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442855328.29498.30.camel@transmode.se \
--to=joakim.tjernlund@transmode.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 NNTP newsgroup(s).