All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Rafael Dulfer <rafael@dulfer.be>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
	"Andrei Rybak" <rybak.a.v@gmail.com>,
	"Rafael Dulfer" <rafael.dulfer@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH] rev-list: clarify git-log default date format
Date: Thu, 02 Feb 2023 08:17:09 -0800	[thread overview]
Message-ID: <xmqqfsbovy7u.fsf@gitster.g> (raw)
In-Reply-To: <d9fc8688-bbf1-96c2-07bf-a12fe38625a9@dulfer.be> (Rafael Dulfer's message of "Thu, 2 Feb 2023 12:37:37 +0100")

Rafael Dulfer <rafael@dulfer.be> writes:

> like. "`--date=default` is the default format. It is a custom format
> based on rfc2822".

But the thing is it is *not* custom based on rfc2822.  The default
format came first, 2822 much later.  If I have to guess (and I
shouldn't because I was around back when we invented that format,
but I am lazy and my recollecion hazy), it came straight from the
result of ctime() but with timezone info appended at the end.


  reply	other threads:[~2023-02-02 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 15:57 [PATCH] rev-list: clarify git-log default date format Rafael Dulfer
2023-02-01 18:19 ` Junio C Hamano
2023-02-01 22:28   ` Ævar Arnfjörð Bjarmason
2023-02-01 22:58     ` Junio C Hamano
2023-02-02 11:37       ` Rafael Dulfer
2023-02-02 16:17         ` Junio C Hamano [this message]
2023-02-02 16:53           ` Junio C Hamano
2023-02-16  0:42             ` [PATCH v2] " Junio C Hamano
2023-02-16  2:15               ` Jeff King
2023-02-16  2:58                 ` Junio C Hamano
2023-02-16 16:29               ` [PATCH v3] " Junio C Hamano
2023-02-16 17:24                 ` Jeff King
2023-02-01 22:47   ` [PATCH] " Jeff King

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=xmqqfsbovy7u.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=rafael.dulfer@gmail.com \
    --cc=rafael@dulfer.be \
    --cc=rybak.a.v@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.