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

Re: [PATCH] pretend-sha1: grave bugfix.

From
Junio C Hamano <junkio@cox.net>
Date
Feb 16, 2007, 07:29 UTC
Message-ID
<7v8xeya7bw.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070216050943.GD28894@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Aren't we using this for git-blame --contents?  How'd that ever
> work for a non-empty file?

My guess is that git-blame's blob handling has its own built-in cache to avoid read_sha1_file(), and that single "initial" blob is primed by hand, so read_sha1_file() is usually not called for that object name.

Previous: Shawn O. Pearce
Message 4 of 4 in “pretend-sha1: grave bugfix.”
  1. pretend-sha1: grave bugfix.Junio C Hamano, Feb 16, 2007
  2. Johannes SchindelinFeb 16, 2007
  3. Shawn O. PearceFeb 16, 2007
  4. Junio C HamanoFeb 16, 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.