From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Viet Than <thanhoangviet@gmail.com>, Jakub Wilk <jwilk@jwilk.net>
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v2] time.2: wfix regarding year-2038
Date: Mon, 26 Jul 2021 12:16:35 +0200 [thread overview]
Message-ID: <ac6cbd74-f936-a9c3-904e-91ff8a247924@gmail.com> (raw)
In-Reply-To: <CAL9Lf7xpqJd9dHiRiJnX+WcEmC_Cb0fqvQtcVKfvzrz7WydK2w@mail.gmail.com>
Hi Viet, Jakub,
On 7/25/21 1:51 AM, Viet Than wrote:
>> I suppose this should say "...the clock reaches the time 2**31",
>> and then we can keep the parenthetical as is.
> Thanks for the insight! here's the new patch
Thanks for the review, Jakub!
>
> Cc: Jakub Wilk <jwilk@jwilk.net>
> Signed-off-by: Viet Than <thanhoangviet@gmail.com>
>
Patch applied (manually as it was corrupt).
Thanks,
Alex
> ---
> man2/time.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/time.2 b/man2/time.2
> index 059222dcd..a7410bfc8 100644
> --- a/man2/time.2
> +++ b/man2/time.2
> @@ -93,7 +93,7 @@ specified as NULL cannot fail with the error
> .BR EOVERFLOW ,
> even on ABIs where
> .I time_t
> -is a signed 32-bit integer and the clock ticks past the time 2**31
> +is a signed 32-bit integer and the clock reaches at or beyond the time 2**31
> (2038-01-19 03:14:08 UTC, ignoring leap seconds).
> (POSIX.1 permits, but does not require, the
> .B EOVERFLOW
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2021-07-26 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 15:52 [PATCH] time.2: wfix regarding year-2038 Viet Than
2021-07-24 16:39 ` Jakub Wilk
2021-07-24 23:51 ` [PATCH v2] " Viet Than
2021-07-26 10:16 ` Alejandro Colomar (man-pages) [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=ac6cbd74-f936-a9c3-904e-91ff8a247924@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=thanhoangviet@gmail.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 NNTP newsgroup(s).