git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Danh Doan <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2020, #01; Wed, 15)
Date: Thu, 16 Apr 2020 22:38:16 -0700	[thread overview]
Message-ID: <xmqqr1wmwu2f.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200417022416.GE2285@danh.dev> (Danh Doan's message of "Fri, 17 Apr 2020 09:24:16 +0700")

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.


  reply	other threads:[~2020-04-17  5:38 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 [this message]
2020-04-17 13:36     ` Danh Doan
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=xmqqr1wmwu2f.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=congdanhqx@gmail.com \
    --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.
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 NNTP newsgroup(s).