From: Justin Collum Date: Thu, 08 Aug 2013 23:58:20 GMT Subject: Re: git status resets permissions on index file -- Ubuntu 12.04 64b Message-ID: In-Reply-To: doing sudo chmod 644 ./.git/index instead of 777 resulted in the same result a bit later: $ gs fatal: index file open failed: Permission denied On Thu, Aug 8, 2013 at 3:37 PM, Kyle J. McKay wrote: > On Aug 8, 2013, at 15:18, Andrew Ruder wrote: >> >> On Thu, Aug 08, 2013 at 11:35:35PM +0200, Stefan Beller wrote: >>> >>> On 08/08/2013 10:27 PM, Justin Collum wrote: >>>> >>>> [...] >>>> -rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index >>>> [...] >>>> -rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <--------------- >>> >>> >>> The permissions are set to reading for all and writing for you(r user) >>> and your group. This should be no problem with standard git commands. >>> Before you had the index file executable, why would you need that? >> >> >> I'm about 90% sure the issue he's having is that the write bit for >> other/world goes away and he is neither the user dev or the group dev >> and the reason for all the executable bits is that he is regularly >> running >> >> chmod -R 777 . >> >> Justin, if this is true, I will tell you that git respects your umask >> but I just can't bring myself to really suggest someone type umask 000 >> ever. :( > > > > Justin, > > If you really want a repository that's writable by everyone, why not just do > "git config core.sharedRepository 0666" ? > > If you just want them to be group-writable you may be happier with "git > config core.sharedRepository true" or possibly "git config > core.sharedRepository all". The setting is described fully in "git help > config".