Re: Fixing commit dates before pushing

Eli Zaretskii via Gdb <[email protected]> Tue, 12 May 2026 14:57:53 +0300
Newsgroups gmane.comp.gdb.devel
Message-ID <[email protected]>
> Date: Tue, 12 May 2026 10:19:26 +0200
> From: Tom de Vries via Gdb <[email protected]>
> 
> Hi,
> 
> back in 2014, a requirement was added to the contribution checklist: 
> fixing commit dates ( 
> https://sourceware.org/gdb/wiki/ContributionChecklist#Fixing_commit_dates ).
> 
> The related discussion is here ( 
> https://inbox.sourceware.org/gdb/[email protected]/T/#u ).
> 
> Looking at recent commits, this is done by a few people, but not everybody.
> 
> [ FWIW, I'm using a push script (see below) that takes care of this for 
> me. ]
> 
> If not too many people actually do this, and nobody's complaining about 
> it, should we drop the requirement?

My vote is to drop the requirement.  With all the possible cases which
Git supports of getting a commit into the upstream repository, I don't
think we can guarantee monotonous dates anyway.

However, I push commits only rarely, so my opinion's weight is
probably not too high.