[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8782: date command
From: |
Jim Meyering |
Subject: |
bug#8782: date command |
Date: |
Fri, 03 Jun 2011 10:02:39 +0200 |
Voelker, Bernhard wrote:
> Jim Meyering wrote:
>> James Youngman wrote:
>>
>>> One tweak: use date -d "12:00 +1 day" instead of "date -d tomorrow" in
>>> the example.
>>
>> Good idea. That makes it immune to failure in a one hour interval
>> on the day before the spring DST transition.
>
> hmm, shouldn't the "tomorrow" handling be fixed then?
Hi Voelker,
"Fixed" how? To retry in that very unusual case?
Let's ignore that someone might depend on the current failure,
e.g., to locate a DST transition.
Note that "tomorrow" is equivalent to "+1 day", aka "+24 hours".
Upon retry would you use +23 hours or +25 hours? Something else?
I don't think it's feasible to change it.
This is well documented in the FAQ, and probably in the manual, too.
- bug#8782: date command, Rick Stanley, 2011/06/01
- bug#8782: date command, Pádraig Brady, 2011/06/01
- bug#8782: date command, Jesse Gordon, 2011/06/01
- bug#8782: date command, James Youngman, 2011/06/02
- bug#8782: date command, Jim Meyering, 2011/06/03
- bug#8782: date command, Voelker, Bernhard, 2011/06/03
- bug#8782: date command,
Jim Meyering <=
- bug#8782: date command, Voelker, Bernhard, 2011/06/03
- bug#8782: date command, Paul Eggert, 2011/06/03
- bug#8782: date command, Jim Meyering, 2011/06/03
- bug#8782: date command, Voelker, Bernhard, 2011/06/03
- bug#8782: date command, Jim Meyering, 2011/06/03
- bug#8782: date command, Voelker, Bernhard, 2011/06/03
- bug#8782: date command, Ruediger Meier, 2011/06/03
- bug#8782: date command, Ruediger Meier, 2011/06/03
bug#8782: date command, Bob Proulx, 2011/06/01