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

Re: git-cvsserver doesn't respect core.sharedrepository

From
APAndy Parkins <andyparkins@gmail.com>
Date
Feb 13, 2007, 16:05 UTC
Message-ID
<200702131605.29088.andyparkins@gmail.com>
In-Reply-To
<Pine.LNX.4.63.0702131611010.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On Tuesday 2007 February 13 15:11, Johannes Schindelin wrote:
> Since ref updates are not write-into-existing-file, but rather
> write-into-new-file-and-replace-old, it should work, no?

That perhaps might be the explanation for the bad behaviour. The ref is being updated in git-cvsserver by writing the new head hash into the lockfile then doing

    unlink($reffile);
    rename($lockfile, $reffile);

The lockfile is made with whatever umask is in place, so the sharedrepository=group is being ignored. The solution then is to use the permissions of the existing reffile when creating the lockfile.

Thanks Johannes.  One little sentence and it all becomes clear :-)
Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
Previous: Johannes SchindelinNext: Nicolas Pitre
Message 3 of 7 in “git-cvsserver doesn't respect core.sharedrepository”
  1. Andy ParkinsFeb 13, 2007
  2. Johannes SchindelinFeb 13, 2007
  3. Andy ParkinsFeb 13, 2007
  4. Nicolas PitreFeb 13, 2007
  5. Johannes SchindelinFeb 13, 2007
  6. Andy ParkinsFeb 13, 2007
  7. Martin LanghoffMar 5, 2007

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.