From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Omri Sarig <omri.sarig13@gmail.com>, git@vger.kernel.org
Subject: Re: Understanding why Git defaults to show author date and not committer date
Date: Sat, 11 Jul 2026 13:54:02 -0700 [thread overview]
Message-ID: <xmqq4ii5b639.fsf@gitster.g> (raw)
In-Reply-To: <20260711080331.GB1470749@coredump.intra.peff.net> (Jeff King's message of "Sat, 11 Jul 2026 04:03:31 -0400")
Jeff King <peff@peff.net> writes:
> On Fri, Jul 10, 2026 at 05:08:11PM +0200, Omri Sarig wrote:
>
>> I understand the distinction between the 2 formats, and I can see the utility of
>> both. I'm curious about the decision to show the author date and not the
>> committer date as default one in Git commands.
>> Are there some workflows where the author date is more relevant, or is that
>> mostly a legacy decision?
>>
>> I'd be interested in hearing about workflows where the author date is the more
>> useful one, as I use the committer date almost always.
>
> In a workflow based on mailing patches, the committer date is usually
> much less interesting. It is "when the maintainer happened to pick up
> your patch", as opposed to when you wrote it. Likewise, we show the
> author's name by default, not the committer's.
True. In mailing list workflow, the author date recorded is usually
the date that the patch was sent to the mailing list, which may be
later than when you wrote it, but is much more relevant as that is
closer to the time when anybody other than the author have seen the
patch for the first time.
next prev parent reply other threads:[~2026-07-11 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 15:08 Understanding why Git defaults to show author date and not committer date Omri Sarig
2026-07-11 8:03 ` Jeff King
2026-07-11 20:54 ` Junio C Hamano [this message]
2026-07-12 8:45 ` Oswald Buddenhagen
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=xmqq4ii5b639.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=omri.sarig13@gmail.com \
--cc=peff@peff.net \
/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