Mark Hills <> writes:

> We make extensive use of unix permissions and core.sharedRepository -- 
> multiple developers push to the same repo.
> I have often wondered why core.sharedRepository is needed at all as a 
> separate configuration?
> It looks like it might be easier (and less confusing to users) to derive 
> this attribute from the top-level .git directory?

Hrm, clever ;-)

> Is there a reason why Git doesn't just follow (and echo) the top-level 
> permissions?

Other than "we did not trust that all the end users are capable of
doing the right 'chmod 2775 .git && chgrp project .git", with a
little bit of "we didn't think of that when we wrote the system", I
do not recall any.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to