From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha <libc-alpha@sourceware.org>,
Bruno Haible <bruno@clisp.org>, Thorsten Kukuk <kukuk@suse.com>
Subject: Re: utmp 64 bit time_t support
Date: Fri, 04 Aug 2023 09:28:36 +0200 [thread overview]
Message-ID: <87sf8zqna3.fsf@linux-m68k.org> (raw)
In-Reply-To: <c372beb0-153b-f3c0-4b78-ed7f966a78c3@cs.ucla.edu> (Paul Eggert's message of "Fri, 4 Aug 2023 00:00:15 -0700")
On Aug 04 2023, Paul Eggert wrote:
> Obviously this Gnulib hack won't work after the year 2038,
It could just re-interpret the timestamp field as an unsigned number.
The utmp databases most likely only contain data for a few years at
most, and timestamps from before the epoch are certainly non-existing.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-08-04 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 20:28 Adhemerval Zanella Netto
2023-08-01 20:46 ` Thorsten Kukuk
2023-08-04 7:00 ` Paul Eggert
2023-08-04 7:28 ` Andreas Schwab [this message]
2023-08-05 18:22 ` Paul Eggert
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=87sf8zqna3.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=adhemerval.zanella@linaro.org \
--cc=bruno@clisp.org \
--cc=eggert@cs.ucla.edu \
--cc=kukuk@suse.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).