Re: .git/info/refs

From: Matthias Lederhofer <matled@gmx.net>
Date: Feb 1, 2007, 17:32 UTC
Message-ID: <20070201173234.GA29170@moooo.ath.cx>
In-Reply-To: <45C21BA0.4080700@zytor.com>

H. Peter Anvin <hpa@zytor.com> wrote:

> Yes, it does matter, because it drives the load up further.  If you 
> start having this going on in overlapping instances, then you're soon on 
> the downhill slope of a cascading failure.

Add some other locking mechanism.

> And we have already experimented with it.  It unfortunately doesn't help 
> much, it only makes matters worse.

The gitweb overview page has less than one hit per minute? Otherwise this should help.

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