From: Zefram <zefram@fysh.org>
To: 26164@debbugs.gnu.org
Subject: bug#26164: time-difference mishandles leap seconds
Date: Wed, 19 Apr 2017 17:22:03 +0100 [thread overview]
Message-ID: <20170419162203.GE6765@fysh.org> (raw)
In-Reply-To: <87d1c8mprz.fsf@igalia.com>
Andy Wingo wrote:
>Makes sense to me. Would you like to submit a patch and test case?
This particular bug has interactions with other bugs that make me
uncomfortable about attempting to fix it right now. The right way to
fix this is especially influenced by the approach taken to bug#22033 and
to the bug regarding pre-1972 UTC. The latter I haven't even reported
yet because it's difficult to formulate in the presence of some of the
other UTC-related bugs such as bug#21911 and bug#21912. So I think this
is one to postpone until some of those are out of the way.
-zefram
next prev parent reply other threads:[~2017-04-19 16:22 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 [this message]
2018-10-21 22:56 ` Mark H Weaver
2018-11-05 11:02 ` Zefram
2018-11-05 13:47 ` John Cowan
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=20170419162203.GE6765@fysh.org \
--to=zefram@fysh.org \
--cc=26164@debbugs.gnu.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).