Mark Hills [off-list ref] writes:
quoted
quoted
It looks like it might be easier (and less confusing to users) to derive
this attribute from the top-level .git directory?
Hrm, clever ;-)
quoted
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.
Thanks. If I understand, you mean it might be worth a try to implement
this.
Not really.
I still do not think that all the end users are capable of doing the
right 'chmod 2775 .git && chgrp project .git' themselves.
On Wed, 17 Oct 2012, Junio C Hamano wrote:
Mark Hills [off-list ref] writes:
quoted
quoted
quoted
It looks like it might be easier (and less confusing to users) to derive
this attribute from the top-level .git directory?
Hrm, clever ;-)
quoted
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.
Thanks. If I understand, you mean it might be worth a try to implement
this.
Not really.
I still do not think that all the end users are capable of doing the
right 'chmod 2775 .git && chgrp project .git' themselves.
But with the current method, users still have to do this _and_ set
sharedRepository=.
It would make things hard or impossible if we assume that a user wanting
to share a repository does not understand file modes or groups.
--
Mark