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

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

From
FFMorschel <git@fmorschel.dev>
Date
Aug 5, 2025, 11:47 UTC
Message-ID
<09e2fb55-2f04-44db-a062-fa6c2c01c8eb@fmorschel.dev>
In-Reply-To
<d7ey5l2bcy4xzidqyq5by4mrwgziahypvnco5ilbik4y3feqhj@vspbafxowl5l>
Show 28 quoted lines
> 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!
>
Previous: Konstantin KhomoutovNext: Junio C Hamano
Message 7 of 10 in “Feature Request: git mv --after (new flag)”
  1. FMorschelAug 4, 2025
  2. Konstantin KhomoutovAug 4, 2025
  3. FMorschelAug 4, 2025
  4. Kristoffer HaugsbakkAug 4, 2025
  5. Junio C HamanoAug 4, 2025
  6. Konstantin KhomoutovAug 5, 2025
  7. FMorschelAug 5, 2025
  8. Junio C HamanoAug 6, 2025
  9. Johannes SixtAug 5, 2025
  10. Junio C HamanoAug 5, 2025

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.