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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Junio C Hamano <junkio@xxxxxxx> wrote:
> 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.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]