Allowing a group to access a master hg repo under linux

[Marko Käning]

Hi Giorgos,

> `chmod -R g+w .hg' and a umask of 002 should be enough, don't set the
> g+s flag.  Mercurial will then create files with the right permissions
> to allow writes by group members.

umask 0002 is what I thought should be necessary, but although the various 
ssh login shells are set to 0022 mercurial still creates all files and 
directories with write access also for groups. Looks as if hg takes care 
of this internally and does not rely on or limit itself by the shell's 
settings. Is this true? Or am I missing something here?

I wonder why the s flag is not necessary or wanted. I thought it is 
necessary to let the created files have the correct user/group.

Thanks for your response.

Greets,
Marko