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

Re: [PATCH 2/2] Use cache_sha1_file() in git-blame and git-merge-recursive.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 5, 2007, 05:56 UTC
Message-ID
<20070205055659.GA13472@spearce.org>
In-Reply-To
<7v7iuxp2xt.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 5 quoted lines
> git-blame needs to register an arbitrary data to in-core index
> while annotating a working tree file (or standard input), but
> git-blame is a read-only application and the user of it could
> even lack the privilege to write into the object store; it is
> another good example for cache_sha1_file().
*Excellent* reason for this.
But what about pretend_sha1_file() instead?

The term 'cache' suggests to me (on first glance) that its loading an existing object and caching it in memory for faster, frequent access, when compared to other non-cached objects.

-- 
Shawn.
Previous: Junio C Hamano
Message 2 of 2 in “Use cache_sha1_file() in git-blame and git-merge-recursive.”
  1. 2/2 Use cache_sha1_file() in git-blame and git-merge-recursive.Junio C Hamano, Feb 5, 2007
  2. Shawn O. PearceFeb 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.