From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] gmtime() ulong
Date: Mon, 3 Jun 2013 20:09:33 +0100 [thread overview]
Message-ID: <07ceecfd621281a30ced4eb9226e0c24@hamnavoe.com> (raw)
In-Reply-To: <9fd46f174ab35243e649a8cec6705de6@gmx.de>
I can't mind-read the intention of the change, but the effect
is to do unsigned div/mod instead of signed. This allows the
time value to be treated as an unsigned 32-bit number, so we
should be looking at a 2106 problem not a 2038 problem.
Unfortunately while gmtime() is right, asctime() is getting
its centuries in a twist:
term% date 4070930400
Thu Jan 1 06:00:00 GMT 2099
term% date 4102466400
Fri Jan 1 06:00:00 GMT 2000
next prev parent reply other threads:[~2013-06-03 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 23:31 cinap_lenrek
2013-06-03 1:03 ` cinap_lenrek
2013-06-03 2:28 ` erik quanstrom
2013-06-03 19:09 ` Richard Miller [this message]
2013-06-03 19:11 ` erik quanstrom
2013-06-03 19:15 ` Richard Miller
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=07ceecfd621281a30ced4eb9226e0c24@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).