From: John Cowan <cowan@ccil.org>
To: Mark H Weaver <mhw@netris.org>
Cc: zefram@fysh.org, 22034@debbugs.gnu.org, 22034-done@debbugs.gnu.org
Subject: bug#22034: time-utc->date shows bogus zone-dependent leap second
Date: Mon, 29 Oct 2018 20:23:22 -0400 [thread overview]
Message-ID: <CAD2gp_T3tGVus7wx1cHsEenONhOZ=nR6jGyBV0_a0P8apug8zg@mail.gmail.com> (raw)
In-Reply-To: <87a7mx8boh.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Mon, Oct 29, 2018 at 3:17 AM Mark H Weaver <mhw@netris.org> wrote:
Can you please be more concrete and tell me what numbers you think
> should be in the second column, to properly reflect the column heading?
> I'm not asking for a prose description, but for the actual numbers.
>
Here you go:
+-------------------------------------------------------------------------+
| TAI seconds UTC seconds Posix seconds |
| since since since |
| midnight TAI midnight UTC midnight UTC |
| 1 Jan 1970 1 Jan 1970 1 Jan 1970 Result of 'time-tai->date' |
|-------------------------------------------------------------------------|
|$2 = ((126230410 126230398 126230398 "1973-12-31T23:59:58Z") |
| (126230411 126230399 126230399 "1973-12-31T23:59:59Z") |
| (126230412 126230400 126230400 "1973-12-31T23:59:60Z") |
| (126230413 126230401 126230400 "1974-01-01T00:00:00Z") |
| (126230414 126230402 126230401 "1974-01-01T00:00:01Z")) |
+-------------------------------------------------------------------------+
So as you see leap seconds are included in both the TAI and the UTC count,
but not in the Posix count.
--
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
I could dance with you till the cows come home. On second thought,
I'd rather dance with the cows when you come home.
--Rufus T. Firefly
[-- Attachment #2: Type: text/html, Size: 2478 bytes --]
next prev parent reply other threads:[~2018-10-30 0:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 19:51 bug#22034: time-utc->date shows bogus zone-dependent leap second Zefram
2018-10-20 21:42 ` Mark H Weaver
2018-10-22 2:38 ` John Cowan
2018-10-22 6:12 ` Mark H Weaver
2018-10-25 22:21 ` John Cowan
2018-10-28 20:39 ` Mark H Weaver
2018-10-28 23:58 ` John Cowan
2018-10-29 7:16 ` Mark H Weaver
2018-10-29 22:33 ` Mark H Weaver
2018-10-30 0:23 ` John Cowan [this message]
2018-10-30 2: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_T3tGVus7wx1cHsEenONhOZ=nR6jGyBV0_a0P8apug8zg@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=22034-done@debbugs.gnu.org \
--cc=22034@debbugs.gnu.org \
--cc=mhw@netris.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).