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

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

From
Johannes Sixt <j6t@kdbg.org>
Date
Aug 5, 2025, 06:03 UTC
Message-ID
<4d08a37e-2c12-4e3b-b6a6-028e2d6c0a22@kdbg.org>
In-Reply-To
<2f505f75-112a-4b71-bb05-ea0cb7731cd7@fmorschel.dev>
Am 04.08.25 um 16:05 schrieb FMorschel:
Show 7 quoted lines
> This is a request to add an –after mode to git mv command to explicitly 
> mark a filesystem rename after it has occurred (analogous to mercurial 
> => hg mv –after).
> 
> This would allow IDE/Language refactor renames/moves and would make sure 
> git still detects the moves correctly for keeping the correct commit 
> history.

I've wished for this feature several times already. Though, in Git parlance it would be spelled `git mv --cached`.

-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 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.