From: Carlos O'Donell <carlos@redhat.com>
To: Fabian Koch <fabian.koch@de.abb.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: Y2038 Proofness roadmap
Date: Fri, 23 Mar 2018 15:49:00 -0000 [thread overview]
Message-ID: <fb572e9c-4a23-2ee8-0551-21a63880b2ac@redhat.com> (raw)
In-Reply-To: <HE1PR06MB10365D4271AC2C90564412E1D9A80@HE1PR06MB1036.eurprd06.prod.outlook.com>
On 03/23/2018 03:34 AM, Fabian Koch wrote:
> Dear all,
>
> can I ask about the roadmap for the Y2038 Proofness Design found at https://sourceware.org/glibc/wiki/Y2038ProofnessDesign?
> I need the 64bit time_t type on a 32bit system, so I'm very eager to have this integrated into glibc.
>
> Any infos on time frame or planning about this would be greatly appreciated.
The plan is to review the changes and get them merged before 2038 :-)
Help reviewing would be much appreciated.
Please feel free to review Albert's latest patches.
--
Cheers,
Carlos.
prev parent reply other threads:[~2018-03-23 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 10:34 Fabian Koch
2018-03-23 15:49 ` Carlos O'Donell [this message]
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=fb572e9c-4a23-2ee8-0551-21a63880b2ac@redhat.com \
--to=carlos@redhat.com \
--cc=fabian.koch@de.abb.com \
--cc=libc-alpha@sourceware.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).