* cache for copy/rename detection
@ 2006-11-26 12:59 Nguyen Thai Ngoc Duy
0 siblings, 0 replies; only message in thread
From: Nguyen Thai Ngoc Duy @ 2006-11-26 12:59 UTC (permalink / raw)
To: git
I thought about this lately. git's expensive copy/rename detection can
be run once and the results are kept somewhere in .git. Copy/rename
detection depends on tree objects and git detection algorithm. Tree
objects are immutable and git algorithm change rate is low IMO. So
cache invalidation is unlikely to happen.
Another thing I want to do with this cache is ability to manually
inject some hints to git. For example, I remove a file. Several
commits later, I revive that file in another place. I know that two
files are the same but can't tell git (and I don't think Git will
detect this pattern). With this cache, I can tell git this file is a
copy of that file.
What do you think?
--
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-11-26 12:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-26 12:59 cache for copy/rename detection Nguyen Thai Ngoc Duy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).