Hi Warner,
> But consider TAI and UTC when they were equal, for the sake of
> argument. I know they never were, but if we look at what the first one
> would look like:
That's a nice, clear example. Thanks.
> 23:59:58 23:59:580
> 23:59:59
On 2017-02-03 04:30 PM, Warner Losh wrote:
On Wed, Feb 1, 2017 at 11:14 PM, Warner Losh wrote:
On Wed, Feb 1, 2017 at 10:37 PM, Zefram wrote:
Warner Losh wrote:
If you are going to willfully misunderstand, then I'm done being patient.
I am not willfully misunderstanding. I have tried to un
On 2017-02-03 16:30, Warner Losh wrote:
On Wed, Feb 1, 2017 at 11:14 PM, Warner Losh wrote:
On Wed, Feb 1, 2017 at 10:37 PM, Zefram wrote:
Warner Losh wrote:
If you are going to willfully misunderstand, then I'm done being patient.
I am not willfully misunderstanding. I have tried to und
On Wed, Feb 1, 2017 at 11:14 PM, Warner Losh wrote:
> On Wed, Feb 1, 2017 at 10:37 PM, Zefram wrote:
>> Warner Losh wrote:
>>>If you are going to willfully misunderstand, then I'm done being patient.
>>
>> I am not willfully misunderstanding. I have tried to understand
>> what you're doing, and
In message , Tony Finch
writes:
>This is an interesting proposal for fixing the Cloudflare leap second bug,
>so that time interval calculations do sensible things even when the clock
>is reset, without making an incompatible change to the existing APIs.
>
>https://github.com/golang/propo
About whether dTAI is 36 or 37 before/during/after the 2016 leap second --
here's another way to appreciate what's going on with UTC time scale tectonics.
The UTC spec allows for positive and negative leap seconds, and by current
convention they are limited to at most one per month. This means -
This is an interesting proposal for fixing the Cloudflare leap second bug,
so that time interval calculations do sensible things even when the clock
is reset, without making an incompatible change to the existing APIs.
https://github.com/golang/proposal/blob/master/design/12914-monotonic.md
Tony.
