<div dir="ltr">Hi,<div><br></div><div>changing the default umask on the entire server is not necessary to fix this problem. Git already has support for exactly this use case---it will set the file permissions correctly, we just need to specify that this is a shared repository.</div>
<div>The command to run is:</div><div><br></div><div>git config core.sharedRepository true</div><div><br></div><div>(I missed the "core" in my previous e-mail, and I just noticed that my correction went only to Austin).</div>
<div><br></div><div>-Iavor</div><div><br></div><div><div> core.sharedRepository</div><div><br></div><div> When group (or true), the repository is made shareable between</div><div> several users in a group (making sure all the files and objects are</div>
<div> group-writable).</div><div><br></div><div> When all (or world or everybody), the repository</div><div> will be readable by all users, additionally to being</div><div> group-shareable.</div>
<div><br></div><div> When umask (or false), git will use permissions</div><div> reported by umask(2).</div><div><br></div><div> When 0xxx, where 0xxx is an octal number,</div><div> files in the repository will have this mode value. 0xxx will</div>
<div> override user’s umask value (whereas the other options will only</div><div> override requested parts of the user’s umask value).</div><div><br></div><div> Examples: 0660</div><div> will make the repo read/write-able for the owner and group, but</div>
<div> inaccessible to others (equivalent to group unless umask is e.g.</div><div> 0022). 0640 is a repository that is group-readable but not</div><div> group-writable. See git-init(1). False by default.</div>
</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 22, 2013 at 3:11 PM, Ian Lynagh <span dir="ltr"><<a href="mailto:ian@well-typed.com" target="_blank">ian@well-typed.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Jul 22, 2013 at 10:56:45AM +0100, Simon Marlow wrote:<br>
><br>
> I vaguely recall that we used to do this with a post-commit hook to<br>
> do a 'chmod g+w -R' on the tree.<br>
<br>
</div>I've now set the default umask on the new server to be 002, and I've<br>
chmod'ed the current trees, so I think it will be OK now.<br>
<br>
<br>
Thanks<br>
<span class="HOEnZb"><font color="#888888">Ian<br>
--<br>
Ian Lynagh, Haskell Consultant<br>
Well-Typed LLP, <a href="http://www.well-typed.com/" target="_blank">http://www.well-typed.com/</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/ghc-devs" target="_blank">http://www.haskell.org/mailman/listinfo/ghc-devs</a><br>
</div></div></blockquote></div><br></div>