Re: git mv after the fact
- From
Chris Torek <chris.torek@gmail.com>
- Date
- May 26, 2026, 16:40 UTC
- Message-ID
- <CAPx1Gvd9+z0th9whCbcA60_bWproPp+kwp3qDmhQOe4G=0=E6A@mail.gmail.com>
- In-Reply-To
- <02663c67-01ad-4dd1-aae6-9e9706f3d040@fhannenheim.net>
On Tue, May 26, 2026 at 6:18 AM Frieder Hannenheim <mail@fhannenheim.net> wrote:
> 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. ...
You may already know this, but technically no flag is needed: you can just "git add" the new name and "git rm" the old one, with the same effect.
A flag for "git mv" would be convenient (and slightly more efficient, not in terms of storage but in terms of CPU time spent discovering that the contents under the new name already exist in the object database). But Git will discover the rename on its own in the usual way regardless of how you get to that point.
Chris