From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: FMorschel <git@fmorschel.dev>, git@vger.kernel.org
Cc: "Konstantin Khomoutov" <kostix@bswap.ru>
Subject: Re: Feature Request: git mv --after (new flag)
Date: Mon, 04 Aug 2025 18:04:05 +0200 [thread overview]
Message-ID: <ddc841ec-bc4b-4c01-a99e-9a65af3963bc@app.fastmail.com> (raw)
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. :)
next prev parent reply other threads:[~2025-08-04 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1fa7a8d8-3ae5-4913-b3b5-21d8f67e567d@fmorschel.dev>
[not found] ` <0afc01b2-11a2-4f77-a858-7a444e8bb1d4@fmorschel.dev>
2025-08-04 14:05 ` Feature Request: git mv --after (new flag) FMorschel
2025-08-04 15:02 ` Konstantin Khomoutov
2025-08-04 15:53 ` FMorschel
2025-08-04 16:04 ` Kristoffer Haugsbakk [this message]
2025-08-04 16:28 ` Junio C Hamano
2025-08-05 9:36 ` Konstantin Khomoutov
2025-08-05 11:47 ` FMorschel
2025-08-06 5:17 ` Junio C Hamano
2025-08-05 6:03 ` Johannes Sixt
2025-08-05 15:42 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ddc841ec-bc4b-4c01-a99e-9a65af3963bc@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@fmorschel.dev \
--cc=git@vger.kernel.org \
--cc=kostix@bswap.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).