Re: Feature Request: git mv --after (new flag)

[FMorschel <git@fmorschel.dev>]

> On 05/08/2025 06:36, Konstantin Khomoutov wrote:
>> FMorschel, when reading, consider paying close attention to the two things:
>>
>>   - What Linus says about much of the code coming in in the form of the
>>     textual patches mailed to the various mailing lists.
>
>
> I see that now, thanks for the link and for pointing it out.
>
>>   - An example describing a commit which has unified 5 different code snippets
>>     into one.
>>
>> Basically, these bits highlight the fact that files, albeit useful and
>> ubiquitous on today's commodity operating systems, frame our way of thinking
>> of how information is tracked a bit too much ;-)
>
> I never had thought of that.
>
> My only push-back against this decision would be to allow the 
> developer (that actually _understands_ the changes) the ability to 
> make the decision of tracking that.
>
> But since the decision (of what is related to what) is that this 
> should mainly be handled by the threshold (so git can figure it out 
> for you) it's fine then.
>
> Thank you all for taking the time to answer me!
>