All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: FMorschel <git@fmorschel.dev>,
	 git@vger.kernel.org,  "Konstantin Khomoutov" <kostix@bswap.ru>
Subject: Re: Feature Request: git mv --after (new flag)
Date: Mon, 04 Aug 2025 09:28:36 -0700	[thread overview]
Message-ID: <xmqqwm7j59vv.fsf@gitster.g> (raw)
In-Reply-To: <ddc841ec-bc4b-4c01-a99e-9a65af3963bc@app.fastmail.com> (Kristoffer Haugsbakk's message of "Mon, 04 Aug 2025 18:04:05 +0200")

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

> 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/

Thanks for giving this URL so that I do not have to ;-)

>
>> 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. :)

  reply	other threads:[~2025-08-04 16:28 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
2025-08-04 16:28           ` Junio C Hamano [this message]
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=xmqqwm7j59vv.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@fmorschel.dev \
    --cc=git@vger.kernel.org \
    --cc=kostix@bswap.ru \
    --cc=kristofferhaugsbakk@fastmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.