From: John Cowan <cowan@ccil.org>
To: zefram@fysh.org
Cc: 26164@debbugs.gnu.org
Subject: bug#26164: time-difference mishandles leap seconds
Date: Mon, 5 Nov 2018 08:47:46 -0500 [thread overview]
Message-ID: <CAD2gp_R5d21iORE2V87DYs99MCULpyPgZOduUudO5xJL--rmfw@mail.gmail.com> (raw)
In-Reply-To: <20181105110236.ypop5ihwnajobcqs@fysh.org>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Mon, Nov 5, 2018 at 6:03 AM Zefram <zefram@fysh.org> wrote:
Mark H Weaver wrote:
>
> No, that's not how UTC works.
Everything Zefram says is what I was trying to say and failing.
I would only add that:
1) TAI-UTC refers to broken-down time, not to the count
of seconds since some epoch. TAI-UTC is currently 37 seconds, which means
that at 2018-11-05T13:43:00 UTC time (approximately when I am writing this)
it is
2018-11-05T13:43:37 TAI time.
2) Posix time, unlike UTC really does label leap seconds with the same
integer as the
preceding second.
> >Having said all of this, I should admit that I'm not an expert on time
> >standards,
>
> I am.
>
He is.
--
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
There is no real going back. Though I may come to the Shire, it will
not seem the same; for I shall not be the same. I am wounded with
knife, sting, and tooth, and a long burden. Where shall I find rest?
--Frodo
[-- Attachment #2: Type: text/html, Size: 1819 bytes --]
next prev parent reply other threads:[~2018-11-05 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 22:41 bug#26164: time-difference mishandles leap seconds Zefram
2017-04-19 14:32 ` Andy Wingo
2017-04-19 16:22 ` Zefram
2018-10-21 22:56 ` Mark H Weaver
2018-11-05 11:02 ` Zefram
2018-11-05 13:47 ` John Cowan [this message]
2018-11-05 20:46 ` Mark H Weaver
2018-11-06 0:12 ` Mark H Weaver
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD2gp_R5d21iORE2V87DYs99MCULpyPgZOduUudO5xJL--rmfw@mail.gmail.com \
--to=cowan@ccil.org \
--cc=26164@debbugs.gnu.org \
--cc=zefram@fysh.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 read-only IMAP folder(s) and NNTP newsgroup(s).