git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Mathias Rav" <m@git.strova.dk>
Cc: git@vger.kernel.org,  "Phillip Wood" <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] rebase -i: use same commit's message and date with f -C
Date: Tue, 23 Sep 2025 14:38:53 -0700	[thread overview]
Message-ID: <xmqqldm4onma.fsf@gitster.g> (raw)
In-Reply-To: <92d4d585-09e9-4f1d-a471-1ad6b312fa61@app.fastmail.com> (Mathias Rav's message of "Tue, 23 Sep 2025 10:55:02 +0200")

"Mathias Rav" <m@git.strova.dk> writes:

> In `git rebase -i` with the fixup command, the -C flag controls whether
> the commit message is taken from the previous or current commit,
> but currently the author name, email and date are always taken from the
> previous commit.

As the name of the command says, you are fixing up the previous one,
so I do not find it a problem if the credit for writing the
resulting combined commit stays with the author of the previous one.
The authorship information both covers the contents recorded in the
commit's tree, as well as the commit message.

Granted, many commits of this project that is a one-liner change
often have 50 lines of explanation in the commit log message, but
still I think it is sensible to give more authorship credit to the
author of the contents the tree of the final commit than to the
author of the log message of the final commit.

> Change the behavior so that fixup with -C takes both message and author
> from the current commit, instead of taking the author from the previous.

I am somewhat negative to this change.  I am perfectly fine to have
a separate "I may have started from that previous one, but that was
so broken that I essentially dismantled the original and replaced
with the new one.  It is better to attribute the credit to whoever
did this last one that is replacing" command.  But the "fixup"
command people have been familiar with would be different, I would
think.

  parent reply	other threads:[~2025-09-23 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23  8:55 [PATCH] rebase -i: use same commit's message and date with f -C Mathias Rav
2025-09-23  9:21 ` Karthik Nayak
2025-09-23 15:23 ` Phillip Wood
2025-09-23 17:10 ` Ben Knoble
2025-09-23 17:37 ` Kristoffer Haugsbakk
2025-09-23 21:38 ` Junio C Hamano [this message]
2025-09-24  8:47   ` Johannes Sixt
2025-09-24 13:48     ` Phillip Wood
2025-09-24 15:21     ` Mathias Rav
2025-09-25 10:11       ` Phillip Wood
2025-09-25 17:08         ` Junio C Hamano
2025-09-24 16:54 ` Oswald Buddenhagen
2025-09-24 20:48   ` Junio C Hamano
2025-09-25 10:08     ` Phillip Wood

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=xmqqldm4onma.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=m@git.strova.dk \
    --cc=phillip.wood@dunelm.org.uk \
    /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).