Re: using oldest date when squashing commits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 2023-10-27 08:45, Oswald Buddenhagen wrote:
On Fri, Oct 27, 2023 at 08:34:40AM -0400, Marc Branchaud wrote:
I never use "fixup -C" (or -c), but I do use squash/fixup a lot.  I find that I would prefer it if Git used the most recent Author date from the set of commits being combined, rather than preserving the picked commit's Author date.

that would be unreliable, as plain amends wouldn't be reflected. that may be rare in your workflow, but still.

I'm not talking about amends, plain or otherwise. I'm talking about fixup/squash.

(Why do you focus so much an making rebase and commit behave identically? There is no reason to do so just because they happen to share a couple of parameter names.)

Sometimes it takes quite a while for me to get a piece of work sorted out, and I would rather have the Author date in the end-result commit reflect the work's completion time than its initiation time.

afaict, you need to get used to `--amend --reset-author` all commits before you push to achieve this reliably. that can be easily automated by using -x with rebase -i (filter-repo (ex filter-branch) would also work).

Yes, I know how to force my desired author date on commits, thanks.

		M.




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux