From: Eric Blake <ebb9@byu.net>
To: cygwin@cygwin.com
Subject: 64-bit time_t?
Date: Thu, 17 Sep 2009 11:26:00 -0000 [thread overview]
Message-ID: <4AB21CCC.8030205@byu.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is the transition to 1.7 a good time to change the ABI and offer a 64-bit
time_t type that won't overflow in 2038? Would we have to do the same
sort of transition magic as was done back in 1.5 for 32-bit vs. 64-bit off_t?
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqyHMsACgkQ84KuGfSFAYDWGwCfeNEhefLmrz9u+0A135ZLbLzO
LacAn3BUdTXa8I8RwxHCSZKyK1JQweCS
=QhZR
-----END PGP SIGNATURE-----
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2009-09-17 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 11:26 Eric Blake [this message]
2009-09-17 15:30 ` Christopher Faylor
2009-09-21 19:30 ` Christopher Faylor
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=4AB21CCC.8030205@byu.net \
--to=ebb9@byu.net \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).