From: Junio C Hamano <gitster@pobox.com>
To: Damien Regad <dregad@mantisbt.org>
Cc: git@vger.kernel.org
Subject: Re: Date in git-commit output inconsistent with log.date format
Date: Mon, 16 May 2022 09:14:38 -0700 [thread overview]
Message-ID: <xmqqmtfh4fpt.fsf@gitster.g> (raw)
In-Reply-To: <CA+zp4VNWMxZ2ieS8KP2-uUu90AMmdzyR31VGkf78KdG4jY4eug@mail.gmail.com> (Damien Regad's message of "Mon, 16 May 2022 14:42:05 +0200")
Damien Regad <dregad@mantisbt.org> writes:
> I was amending a commit message, and noticed the date in the output is
> printed in 'default' format, as shown below:
>
> $ git commit --amend --no-edit
> [x bf63ada92] Test commit
> Date: Mon May 16 14:25:57 2022 +0200
> 1 file changed, 32 insertions(+)
> create mode 100644 test.txt
>
> Since I have set log.date=iso, I was expecting the date to use the
> Is it intentional that the
> default format is applied instead ?
Yes.
That output is from "git commit", and is not from any command in the
"git log" family. Besides, it way predates the introduction of
log.date configuration variable.
This could be a XY problem. Can you tell us why you care? What
motivates you to see that date (and optionally Author when the
author is different from the current user) output in a specific
format---it is meant for human consumption so "I run 'git commit' in
a script and scrape its output" would not be it.
Thanks.
prev parent reply other threads:[~2022-05-16 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 12:42 Date in git-commit output inconsistent with log.date format Damien Regad
2022-05-16 16:14 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmtfh4fpt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dregad@mantisbt.org \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).