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

Re: [PATCH] gitweb: New feature last_modified_ref.

From
Junio C Hamano <junkio@cox.net>
Date
Dec 29, 2006, 19:12 UTC
Message-ID
<7vlkkqms8n.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20061229185805.GF6558@localhost>

I somehow suspect this is solving the problem with a wrong tradeoff.

This change only affects the project list page, which I think is simpler to deal with more aggressive caching (say, no more than once every 10 minutes even if some project pushed a new head in the meantime).

Not a firm refusal, but something to think about.
Previous: Robert FitzsimonsNext: Robert Fitzsimons
Message 2 of 3 in “gitweb: New feature last_modified_ref.”
  1. gitweb: New feature last_modified_ref.Robert Fitzsimons, Dec 29, 2006
  2. Junio C HamanoDec 29, 2006
  3. Robert FitzsimonsDec 30, 2006

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.