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

git mv after the fact

From
FHFrieder Hannenheim <mail@fhannenheim.net>
Date
May 26, 2026, 12:57 UTC
Message-ID
<02663c67-01ad-4dd1-aae6-9e9706f3d040@fhannenheim.net>
Hi,

I'd like to propose a new flag for git mv, that updates the index like git mv normally would but does not move the file. This would come in handy when the file has already been moved, or is renamed by some external tool and the user wants to fix up the index afterwards.

Thank you for considering this.

Sincerely, Frieder Hannenheim

Next: Chris Torek
Message 1 of 10 in “git mv after the fact”
  1. Frieder HannenheimMay 26, 2026
  2. Chris TorekMay 26, 2026
  3. Frieder HannenheimMay 26, 2026
  4. Ben KnobleMay 26, 2026
  5. Junio C HamanoMay 27, 2026
  6. Chris TorekMay 27, 2026
  7. Junio C HamanoMay 27, 2026
  8. Ben KnobleMay 28, 2026
  9. Junio C HamanoMay 28, 2026
  10. Tim TassonisMay 27, 2026

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.