Re: sharedRepository derived from file permissions

2012-10-17 Thread Mark Hills
On Wed, 17 Oct 2012, Junio C Hamano wrote: > Mark Hills 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 e

Re: sharedRepository derived from file permissions

2012-10-17 Thread Junio C Hamano
Mark Hills 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

Re: sharedRepository derived from file permissions

2012-10-17 Thread Mark Hills
On Mon, 8 Oct 2012, Junio C Hamano wrote: > 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? >

Re: sharedRepository derived from file permissions

2012-10-08 Thread Junio C Hamano
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 t

sharedRepository derived from file permissions

2012-10-08 Thread Mark Hills
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 attribut