Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen via Gdb <gdb@sourceware.org>
To: Simon Marchi <simark@simark.ca>, Tom de Vries <tdevries@suse.de>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Fixing commit dates before pushing
Date: Tue, 12 May 2026 14:46:42 -0300	[thread overview]
Message-ID: <0cb15a1d-599b-4a74-b3d7-d355fcebcf98@redhat.com> (raw)
In-Reply-To: <25ae9885-e197-437f-9f98-9b87ff093834@simark.ca>

On 5/12/26 11:15 AM, Simon Marchi via Gdb wrote:
> On 5/12/26 4:19 AM, Tom de Vries via Gdb wrote:
>> 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/20140814083231.GA6283@blade.nx/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?
> I must admit that I have never done this myself, so I am not very
> attached to this rule.
>
> Simon
>
I did see that in the contributor checklist, but since the history log 
already had dates that were out of order, I never bothered with doing 
it. I can start if we think it is important, but for whatever my vote is 
worth, I think we can drop it...

-- 
Cheers,
Guinevere Larsen
It/she


  reply	other threads:[~2026-05-12 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  8:19 Tom de Vries via Gdb
2026-05-12 11:57 ` Eli Zaretskii via Gdb
2026-05-12 14:58   ` Arsen Arsenović via Gdb
2026-05-12 14:15 ` Simon Marchi via Gdb
2026-05-12 17:46   ` Guinevere Larsen via Gdb [this message]
2026-05-14 19:29   ` Tom Tromey
2026-05-15 14:49 ` Andrew Burgess via Gdb
2026-05-26 11:37 ` Tom de Vries via Gdb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0cb15a1d-599b-4a74-b3d7-d355fcebcf98@redhat.com \
    --to=gdb@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=simark@simark.ca \
    --cc=tdevries@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox