Re: git init --bare --shared does not set group for some files/dirs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jul 18, 2010 at 01:14:41PM +0300, Ville Skyttä wrote:
> Hello,
> 
> git init --bare --shared does not set the group for some files.  See below; it 
> did set g+s for all dirs, and did set the group for the root dir, config, 
> HEAD, and objects, but failed to set group for branches, description, hooks, 
> info, and refs.  I discussed/reproduced this on #git today with drizzd and was 
> instructed to post here.
> 
> In particular, I hit a problem with this and the refs dir; members of the 
> desired group (gituser in my example) can not write into it.  I can obviously 
> fix this locally with chgrp, but for which files/dirs should the gituser group 
> be set, and are there some files/dirs that it is intentionally not set?

AFAIK, there are none that intentionally don't have it (at least usually every
file and directory there has the repository group as owner). The usual quick
and dirty rules are:

- For fetching, +r for all regular files, +rx for all directories.
- For pushing, +r for all regular files (but +rw for regular files under
/logs/ if any), +rwx for all directories.

BTW: '/branches/' is used by pre-1.5 remotes stuff and pretty much totally
obsolete.

-Ilari
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]