From: Paul Eggert <eggert@cs.ucla.edu>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
mtk.manpages@gmail.com, linux-man@vger.kernel.org
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] ctime.3: mktime() may modify tm_hour due to tm_isdst
Date: Mon, 11 Oct 2021 08:37:25 -0700 [thread overview]
Message-ID: <6ccf0867-33fe-53f0-0bb9-bf25d09aabb6@cs.ucla.edu> (raw)
In-Reply-To: <a8e09a03-3eb2-d6c0-c662-e3db800fe2fc@gmail.com>
On 10/11/21 3:27 AM, Alejandro Colomar (man-pages) wrote:
> timegm(3) says that you should "avoid their use" because timegm(3) is a
> Linux and BSD extension, but its use can NOT be avoided (well, it can,
> but if not done very carefully, you are likely to introduce bugs due to
> setenv(3) not being thread-safe), so I'd remove that sentence from
> timegm(3). I think it should be in POSIX.
No, NetBSD's mktime_z should be in POSIX, as it nicely generalizes both
mktime and timegm.
mktime_z should also be in glibc, but that's another story....
next prev parent reply other threads:[~2021-10-11 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 10:52 Alejandro Colomar
2021-10-11 10:27 ` Alejandro Colomar (man-pages)
2021-10-11 11:12 ` [PATCH v2 1/2] " Alejandro Colomar
2021-10-11 15:36 ` Paul Eggert
2021-10-15 21:49 ` Alejandro Colomar (man-pages)
2021-10-11 11:12 ` [PATCH v2 2/2] timegm.3: Remove recommendation against use of timegm() Alejandro Colomar
2021-10-11 15:40 ` Paul Eggert
2021-10-15 22:03 ` Alejandro Colomar (man-pages)
2021-10-16 0:20 ` Paul Eggert
2021-10-17 18:02 ` Alejandro Colomar (man-pages)
2021-10-17 22:00 ` Paul Eggert
2021-11-05 0:47 ` Alejandro Colomar (man-pages)
2021-11-08 8:05 ` Paul Eggert
2021-10-11 11:54 ` [PATCH v3 1/2] ctime.3: mktime() may modify tm_hour due to tm_isdst Alejandro Colomar
2021-10-11 11:54 ` [PATCH v3 2/2] timegm.3: Remove recommendation against their use Alejandro Colomar
2021-10-11 15:37 ` Paul Eggert [this message]
2021-10-11 22:05 ` [PATCH] ctime.3: mktime() may modify tm_hour due to tm_isdst Joseph Myers
2021-10-15 21:55 ` Alejandro Colomar (man-pages)
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=6ccf0867-33fe-53f0-0bb9-bf25d09aabb6@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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 read-only IMAP folder(s) and NNTP newsgroup(s).