All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hills <mark@pogo.org.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: sharedRepository derived from file permissions
Date: Wed, 17 Oct 2012 13:25:32 +0100 (BST)	[thread overview]
Message-ID: <1210171258060.22876@wes.ijneb.com> (raw)
In-Reply-To: <7vfw5dpmkv.fsf@alter.siamese.dyndns.org>

On Wed, 17 Oct 2012, Junio C Hamano wrote:

> Mark Hills <mark@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 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

      reply	other threads:[~2012-10-17 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08  9:07 sharedRepository derived from file permissions Mark Hills
2012-10-08 16:46 ` Junio C Hamano
2012-10-16 23:20   ` Mark Hills
2012-10-17  7:46     ` Junio C Hamano
2012-10-17 12:25       ` Mark Hills [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1210171258060.22876@wes.ijneb.com \
    --to=mark@pogo.org.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.