[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30795: Issue with date command and EDT

From: Assaf Gordon
Subject: bug#30795: Issue with date command and EDT
Date: Thu, 15 Mar 2018 01:15:28 -0600
User-agent: Mutt/1.5.24 (2015-08-30)


On Wed, Mar 14, 2018 at 05:22:04PM -0700, Paul Eggert wrote:
> On 03/13/2018 06:42 PM, Assaf Gordon wrote:
> >Therefore it is always recommended to use noon (12pm)
> >as explicit time when adjusting days
> Maybe "date" should default to 12:00 instead of to 00:00 when the time is
> not specified? That would avoid this sort of problem, typically.

Technically it's an easy fix (patch attached),
but it changes a long-standing behavior.

I wonder if it will break some existing scripts that might rely
on being 'midnight'? (even implicitly, because the user isn't aware of
this nuance).

For example, currently '2018-03-15 + 14 hours' is 2pm on March 15th.
With this change, it'll result in 2am on March 16th.

What do you think?


Attachment: 0001-parse-datetime-default-to-noon-for-dates-without-tim.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]