Re: thoughts on setting core.logAllRefUpdates default true for bare repos

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Nov 4, 2009, 19:35 UTC
Message-ID: <vpqzl729j72.fsf@bauges.imag.fr>
In-Reply-To: <alpine.DEB.1.00.0911041422170.2788@felix-maschine>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> I did not have time yet to investigate, but it seems that there are 
> problems with the permissions of shared bare repositories when activating 
> the reflogs.

I can't think of any, and I just tried launching two

while true; do git pull; date > foo.txt ; git add .; git commit -m "xxx"; git push; done

in parallel, with two different users pushing to a --bare --shared repository, and it did work well. But I may very well have missed something.

(and actually, if it causes problem, it's an argument in favor of defaulting to false when core.shared is true, not when core.bare).

Unless I missed something, I think core.logAllRefUpdates should be enabled for bare repos.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

$ 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.