Re: using oldest date when squashing commits
- From
Marc Branchaud <marcnarc@xiplink.com>
- Date
- Oct 27, 2023, 13:46 UTC
- Message-ID
- <3aff8ce6-1cb0-465e-9b7a-db6473713786@xiplink.com>
- In-Reply-To
- <ZTu6cqUec3L2PpUC@ugly>
On 2023-10-27 09:26, Oswald Buddenhagen wrote:
Show 17 quoted lines
> On Fri, Oct 27, 2023 at 09:20:04AM -0400, Marc Branchaud wrote: >> >> 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. >> > but why wouldn't you? your use case of marking the date of completion > naturally covers all ways of amending commits, whether directly or via > squashing.
Please do not presume what my use cases might be. I'm quite happy with commit's behaviour, but not happy with rebase's fixup/squash behaviour because it's too much work to achieve the desired results. (Results which, as I said, I don't care about enough to bother changing anyway).
M.