git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: sharedRepository derived from file permissions

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 8, 2012, 16:46 UTC
Message-ID
<7vhaq4nc7g.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1210080955590.12283@wes.ijneb.com>
Mark Hills <mark@pogo.org.uk> writes:
Show 8 quoted lines
> 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 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.

Previous: Mark HillsNext: Mark Hills
Message 2 of 5 in “sharedRepository derived from file permissions”
  1. Mark HillsOct 8, 2012
  2. Junio C HamanoOct 8, 2012
  3. Mark HillsOct 16, 2012
  4. Junio C HamanoOct 17, 2012
  5. Mark HillsOct 17, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.