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

From: Konstantin Khomoutov <kostix@bswap.ru>
Date: Aug 5, 2025, 09:36 UTC
Message-ID: <d7ey5l2bcy4xzidqyq5by4mrwgziahypvnco5ilbik4y3feqhj@vspbafxowl5l>
In-Reply-To: <ddc841ec-bc4b-4c01-a99e-9a65af3963bc@app.fastmail.com>

On Mon, Aug 04, 2025 at 06:04:05PM +0200, Kristoffer Haugsbakk wrote:

[...]

Show 5 quoted lines

>> Wow, this seems to me a really weird design choice.
>>
>> Do you have any insight on to why is this?
> 
> https://lore.kernel.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org/

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.

 - 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 ;-)