From: Adam Thornton <athornton@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] What does your "cal" show?
Date: Wed, 8 Sep 2021 15:52:28 -0700 [thread overview]
Message-ID: <D6DD7438-6B92-481A-8BEA-450452EB066E@gmail.com> (raw)
In-Reply-To: <CANCZdfpJuHLjU_OvUx=rBQF+2pu=DmdnxLndfYxSAd+4rWeJ8A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1375 bytes --]
Ah, leap seconds. I work for an observatory. Some things are in TAI and some are in UTC. At least now I know what to look for when something is 37 seconds off.
Adam
> On Sep 8, 2021, at 1:36 PM, Warner Losh <imp@bsdimp.com> wrote:
>
>
>
> On Wed, Sep 8, 2021, 7:25 AM Dave Horsfall <dave@horsfall.org <mailto:dave@horsfall.org>> wrote:
> On Wed, 8 Sep 2021, Tony Finch wrote:
>
> > It's even more funny than that :-) They actually went back to the Julian
> > calendar in 1712, and they needed to add back the leap day they skipped in
> > 1700; this extra day became February 30th.
> >
> > https://en.wikipedia.org/wiki/List_of_non-standard_dates#February_30 <https://en.wikipedia.org/wiki/List_of_non-standard_dates#February_30>
>
> Oh, my sainted aunt...
>
> This is the example I give to people who say calendars are easy...
>
> Also, I use it in my screeds against the current observational nature of leap seconds.
>
> Warner
>
> -- Dave
> _______________________________________________
> COFF mailing list
> COFF@minnie.tuhs.org <mailto:COFF@minnie.tuhs.org>
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff <https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff>
> _______________________________________________
> COFF mailing list
> COFF@minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
[-- Attachment #1.2: Type: text/html, Size: 3007 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-09-08 22:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 22:10 Dave Horsfall
2021-09-02 23:40 ` Tom Manos
2021-09-02 23:40 ` Greg 'groggy' Lehey
2021-09-03 0:03 ` Nemo Nusquam
2021-09-03 0:54 ` Grant Taylor via COFF
2021-09-03 1:10 ` Greg 'groggy' Lehey
2021-09-03 4:58 ` Dave Horsfall
2021-09-03 0:58 ` Greg 'groggy' Lehey
2021-09-03 4:47 ` Dave Horsfall
2021-09-03 9:28 ` Tom Ivar Helbekkmo via COFF
2021-09-08 10:24 ` Tony Finch
2021-09-08 13:25 ` Dave Horsfall
2021-09-08 20:36 ` Warner Losh
2021-09-08 22:52 ` Adam Thornton [this message]
2021-09-04 14:03 ` Thomas Paulsen
2021-09-03 13:06 Noel Chiappa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D6DD7438-6B92-481A-8BEA-450452EB066E@gmail.com \
--to=athornton@gmail.com \
--cc=coff@tuhs.org \
--cc=imp@bsdimp.com \
/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 NNTP newsgroup(s).