From: Martin Guy <martinwguy@gmail.com>
Date: Fri, 21 Nov 2025 14:32:41 GMT
Subject: Re: Feature request: git cp
Message-ID: <CAL4-wQra+7HOJ6_qNy+4_tvz7=KApW7yb7BNE6B86JnowschXg@mail.gmail.com>
In-Reply-To: <010b01dc5a7b$4790ee30$d6b2ca90$@nexbridge.com>

On Fri, 21 Nov 2025 at 01:10, <rsbecker@nexbridge.com> wrote:
>
> On November 20, 2025 6:08 PM, Lucas Seiki wrote:
>
> I know this might sound trite or wrong but... does this mean that git log
> can actually detect SHA-1 collisions based on similarity checks of file
> contents?

If a git mv is no more than a git rm and a git add then yes.
If i understand correctly from Linus' fabulous rant, that it does
line matching retrospectively always, so not only will it notice
the split of mp3.c but will also notice that the functions in mp3-util.h
one of which only mad used and one of which only lame used,
have jumped to their new files and mp3-util.h purged.

Staggering

My only regret with git is that it's line-based instead of word-based
as that would see a change from < limit to <= limit as one symbol
change, allowing semantic analysis of program changes but
if it's all retrospective anyway, the line-based change analysis
could gain a word-based mode.

   M