On Mon, 2015-09-21 at 09:48 -0700, Junio C Hamano wrote: > Duy Nguyen <pclo...@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-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
