Re: [LEAPSECS] BBC radio Crowd Science

2017-02-03 Thread Tom Van Baak
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

Re: [LEAPSECS] BBC radio Crowd Science

2017-02-03 Thread Brooks Harris
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

Re: [LEAPSECS] BBC radio Crowd Science

2017-02-03 Thread Stephen Scott
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

Re: [LEAPSECS] BBC radio Crowd Science

2017-02-03 Thread Warner Losh
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

Re: [LEAPSECS] Go API for monotonitc elapsed time measurements

2017-02-03 Thread Poul-Henning Kamp
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