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

Re: What's cooking in git.git (Nov 2008, #05; Sat, 15)

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Nov 16, 2008, 09:20 UTC
Message-ID
<fcaeb9bf0811160120v4954939x244165d6f6b5055e@mail.gmail.com>
In-Reply-To
<7vzlk04hkk.fsf@gitster.siamese.dyndns.org>
On 11/16/08, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
>  * nd/rename-cache (Sat Nov 8 18:27:33 2008 +0700) 2 commits
>   - diffcore-rename: add config option to allow to cache renames
>   - diffcore-rename: support rename cache
>
>  I am moderately negative on this one in its current shape.  We shouldn't
>  have to be storing what can be recomputed (and recomputed differently in
>  later software), and we shouldn't be keeping such cached result
>  indefinitely.

Yeah.. having some way to deprecate the cache if you use a newer version was something I thought about but haven't done. Anyway for all the purposes I want it to do, injecting explicit renames may not work if --find-copies-harder is not given. I think you should drop it.

-- 
Duy
Previous: Junio C Hamano
Message 2 of 2 in “What's cooking in git.git (Nov 2008, #05; Sat, 15)”
  1. Junio C HamanoNov 16, 2008
  2. Nguyen Thai Ngoc DuyNov 16, 2008

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.