On Mon, 8 Oct 2012, Junio C Hamano wrote:
Mark Hills m...@pogo.org.uk 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
Mark Hills m...@pogo.org.uk writes:
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
On Wed, 17 Oct 2012, Junio C Hamano wrote:
Mark Hills m...@pogo.org.uk writes:
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)
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
Mark Hills m...@pogo.org.uk 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
5 matches
Mail list logo