Re: Shared repositories and umask

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 15, 2006, 13:51 UTC
Message-ID: <Pine.LNX.4.63.0602151448590.10593@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <20060215130538.GO31278@pasky.or.cz>

Hi,

On Wed, 15 Feb 2006, Petr Baudis wrote:

Show 15 quoted lines

> Dear diary, on Wed, Feb 15, 2006 at 01:19:07PM CET, I got a letter
> where Martin Mares <mj@ucw.cz> said that...
> > I'm playing with a shared repository and I am still unable to get the
> > file and directory permissions kept correctly, that is writeable to
> > a group.
> > 
> > Setting the `core.sharedrepository' flag helps a bit, but not completely:
> > the object files and directories are group-writeable, but for example new
> > head refs aren't.
> 
>   actually, this is not necessary, since when pushing to shared
> repositories, the new ref is created in the directory as a lockfile and
> then moved over the original ref - this makes the ref updating safe and
> raceless, while also making it enough to have the refs directory
> group-writable.

IIRC the relevant discussion was started by this:

http://thread.gmane.org/gmane.comp.version-control.git/13856

>   Therefore, it shouldn't be actually necessary to meddle with umask
> anymore. The documentation is obsolete; I'll remove the relevant bits
> from Cogito docs.

Basically, if you just want a shared repository, you don't need to set the umask. However, if you want to work in the working directory (multiple users), you have to set the umask (it is not enough that the git tools do that, because you are likely to work with other programs as well).

Hth, Dscho