Re: [Bug?] "git commit --amend" always gives author-date to summary?

[Jeff King <peff@peff.net>]

On Thu, Apr 14, 2016 at 02:07:50PM -0700, Junio C Hamano wrote:

> A simple reproduction.  Doing one of these
> 
>     $ git commit --amend --no-edit
>     $ echo >MSG frotz; git commit --amend -F MSG
> 
> on any commit, whether it is your own commit or somebody else's,
> seems to always show the "Date:" of the original commit, e.g.
> 
>     $ git checkout v2.8.0^0
>     $ git commit --amend --no-edit
>     [detached HEAD a6f2a14] Git 2.8
>      Date: Mon Mar 28 12:19:45 2016 -0700
>      3 files changed, 14 insertions(+), 9 deletions(-)
>     $ git checkout v2.8.0^^2
>     $ git commit --amend --no-edit
>     [detached HEAD df9f57e] Documentation: fix git-p4 AsciiDoc formatting
>      Author: Lars Schneider <larsxschneider@gmail.com>
>      Date: Wed Mar 23 11:59:01 2016 +0100
>      1 file changed, 3 insertions(+), 5 deletions(-)
> 
> I can understand the latter, but I am not sure if it makes sense to
> do the former.  The output is coming from b7242b8c (commit: print
> "Date" line when the user has set date, 2014-05-01), whose objective
> I can agree with, but does not seem to match the use case.

That's working as I intended it in both cases. The point is to show
extra information whenever we have picked an ident or date that is not
the "normal" one. As you noted later, leaving the old author date is the
normal thing for "--amend", but it's still different from a normal
commit that uses the current user and the current date. So I guess it
depends on how you define normal.

IMHO, we are better off generally erring on the side of printing extra
information. The command is already quite chatty, and we are more likely
to remind somebody that they wanted "--reset-author" than to bother
thing.

> [...]
> I suspect that there are people who are already depending on this
> behaviour, so it may not be worth fixing, but I found it somewhat
> irritating (especially after wasting about an hour or so doing wild
> goose chase trying to find a stray invocation of "date" somewhere in
> my script that eventually uses "git commit --amend").
> 
> Thoughts?

So I don't agree that is a "fix" to change it. But if it bothers you, I
don't mind a knob to suppress it in certain cases.

-Peff