From: Danh Doan <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2020, #01; Wed, 15)
Date: Fri, 17 Apr 2020 20:36:47 +0700 [thread overview]
Message-ID: <20200417133647.GA26701@danh.dev> (raw)
In-Reply-To: <xmqqr1wmwu2f.fsf@gitster.c.googlers.com>
On 2020-04-16 22:38:16-0700, Junio C Hamano <gitster@pobox.com> wrote:
> Danh Doan <congdanhqx@gmail.com> writes:
>
> > On 2020-04-15 16:01:52-0700, Junio C Hamano <gitster@pobox.com> wrote:
> >> * dd/iso-8601-updates (2020-04-15) 2 commits
> >> - date.c: allow compact version of ISO-8601 datetime
> >> - date.c: skip fractional second part of ISO-8601
> >>
> >> The approxidate parser learns to parse seconds with fraction.
> >>
> >> Will merge to 'next'.
> >
> > I thought we haven't gained enough concious for "12:34:56.7.days.ago"
> > Current code will treat it as "7 days ago at 12:34:56"
> > New code will treat it as 12:34:56 (today?)
>
> Yup, it clearly is a regression, and I do not think there is an
> agreement that the regression matters in real life.
>
Well, I _think_ we should keep it in pu to see other's feedback for now.
Even if we want to advance it to next, I would like to have this fixup
for the documentation the first patch.
--------------8<-------------
Subject: [PATCH] fixup! date.c: skip fractional second part of ISO-8601
Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
---
Documentation/date-formats.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/date-formats.txt b/Documentation/date-formats.txt
index 6f69ba2ddd..7e7eaba643 100644
--- a/Documentation/date-formats.txt
+++ b/Documentation/date-formats.txt
@@ -20,7 +20,10 @@ RFC 2822::
ISO 8601::
Time and date specified by the ISO 8601 standard, for example
`2005-04-07T22:13:13`. The parser accepts a space instead of the
- `T` character as well. The fractional part will be ignored.
+ `T` character as well. Fractional parts of a second will be ignored,
+ for example `2005-04-07T22:13:13.019` will be treated as
+ `2005-04-07T22:13:13`
+
+
NOTE: In addition, the date part is accepted in the following formats:
`YYYY.MM.DD`, `MM/DD/YYYY` and `DD.MM.YYYY`.
--
Danh
next prev parent reply other threads:[~2020-04-17 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 23:01 What's cooking in git.git (Apr 2020, #01; Wed, 15) Junio C Hamano
2020-04-16 15:28 ` Elijah Newren
2020-04-16 16:37 ` Junio C Hamano
2020-04-16 21:12 ` Damien Robert
2020-04-16 21:30 ` Jeff King
2020-04-16 22:18 ` Junio C Hamano
2020-04-16 22:47 ` Damien Robert
2020-04-16 23:05 ` Damien Robert
2020-04-16 23:34 ` Junio C Hamano
2020-04-17 12:54 ` Damien Robert
2020-04-17 17:30 ` Junio C Hamano
2020-04-17 22:04 ` Damien Robert
2020-04-17 23:22 ` Junio C Hamano
2020-04-18 17:36 ` Damien Robert
2020-04-17 2:24 ` Danh Doan
2020-04-17 5:38 ` Junio C Hamano
2020-04-17 13:36 ` Danh Doan [this message]
2020-04-17 17:40 ` Junio C Hamano
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=20200417133647.GA26701@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.