From: stephen.strowes@gmail.com (sds)
Subject: [TUHS] Leap Second
Date: Wed, 4 Jan 2017 16:54:35 +0100 [thread overview]
Message-ID: <93b155fe-be96-c812-7b67-810d8ecc9e8e@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1701031503360.14104@grey.csi.cam.ac.uk>
On 03/01/2017 16:06, Tony Finch wrote:
> sds <stephen.strowes at gmail.com> wrote:
>
>> Important question: did anybody have an "exciting" new year because of a leap
>> second bug?
> I've been collecting failure reports on the LEAPSECS list
>
> https://pairlist6.pair.net/pipermail/leapsecs/2017-January/thread.html
This is great, thanks!
S.
next prev parent reply other threads:[~2017-01-04 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 23:59 Dave Horsfall
2016-12-29 0:21 ` Peter Jeremy
2017-01-03 10:44 ` sds
2017-01-03 15:06 ` Tony Finch
2017-01-03 15:29 ` Joerg Schilling
2017-01-04 13:32 ` Steffen Nurpmeso
2017-01-04 23:13 ` Warner Losh
2017-01-05 14:29 ` Steffen Nurpmeso
2017-01-04 15:54 ` sds [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-23 23:08 Dave Horsfall
2016-12-23 23:19 ` Michael Kjörling
2016-12-24 1:33 ` Charles Anthony
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=93b155fe-be96-c812-7b67-810d8ecc9e8e@gmail.com \
--to=stephen.strowes@gmail.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).