git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mark Hills <mark@pogo.org.uk>
Cc: git@vger.kernel.org
Subject: Re: sharedRepository derived from file permissions
Date: Wed, 17 Oct 2012 00:46:56 -0700	[thread overview]
Message-ID: <7vfw5dpmkv.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1210170009180.2113@vega> (Mark Hills's message of "Wed, 17 Oct 2012 00:20:56 +0100 (BST)")

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.

  reply	other threads:[~2012-10-17  7:47 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 [this message]
2012-10-17 12:25       ` Mark Hills

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7vfw5dpmkv.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mark@pogo.org.uk \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).