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

[RFC] Cache optimizations

From
Daniel Barkalow <barkalow@iabervon.org>
Date
May 9, 2005, 05:15 UTC
Message-ID
<Pine.LNX.4.21.0505090058240.30848-100000@iabervon.org>

Does anyone know of a reason not to refresh each entry in the cache as it's checked out? It seems to me like this would eliminate the need to call update-cache --refresh after checkout-cache and it would update only the entries for files which are actually changed in the working directory.

Is it just that the code to lock and write the cache is (currently) inconvenient to add to different programs?

	-Daniel
*This .sig left intentionally blank*
Next: Junio C Hamano
Message 1 of 2 in “[RFC] Cache optimizations”
  1. Daniel BarkalowMay 9, 2005
  2. Junio C HamanoMay 9, 2005

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.