Re: Request to add option to interactive rebase to preserve latest commit date

From: Peter Krefting <peter@softwolves.pp.se>
Date: May 7, 2019, 05:45 UTC
Message-ID: <alpine.DEB.2.20.1905070641380.1748@perkele.intern.softwolves.pp.se>
In-Reply-To: <xmqqtve6nbfv.fsf@gitster-ct.c.googlers.com>

Junio C Hamano:

Show 6 quoted lines

> as merely a different way to do the following:
>
> 	$ git commit -m A
> 	$ edit
> 	$ edit further ;# working tree has an equivalent of C
> 	$ git commit --amend -a

Indeed. My last command in the chain is usually

   git commit --amend --date=now

to set the commit date to now. In my use-case it is often a work-in-progress commit that I start out with, which I refine over a couple of hours/days/weeks to get working properly (depending on the complexity of the change), and when I am finally done, the proper dating of the change is "now", not "when I first started doing it".

> I am still not convinced it is a good idea, but I can see how 
> another verb that behaves like existing "fixup" or "squash" but use 
> the authorship not from the updated but from the updating commit 
> might seem useful.

I'd be happy with a parameter and/or configuration variable saying "amend and rebase uses last commit date".

-- 
\\// Peter - http://www.softwolves.pp.se/