Re: Feature Request: git mv --after (new flag)
- From
- Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
- Date
- Aug 4, 2025, 16:04 UTC
- Message-ID
- <ddc841ec-bc4b-4c01-a99e-9a65af3963bc@app.fastmail.com>
- In-Reply-To
- <917aa62f-5f2a-40d7-8fa5-f19a14926241@fmorschel.dev>
On Mon, Aug 4, 2025, at 17:53, FMorschel wrote:
> 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/
> And do you have any idea if this behaviour is tracked to change > somewhere? Maybe by project config? Like, one project could opt-in for > an actual "rename" history.
As a bystander: I’ve never seen anyone involved in this project wanting to track renames as part of the commit.
PS: You need to keep the CC intact when replying on this list. :)