From: Alejandro Colomar <alx@kernel.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bugzilla-daemon@kernel.org, linux-man@vger.kernel.org
Subject: Re: [Bug 221186] New: clock_gettime CLOCK_TAI is incorrectly specified
Date: Sat, 7 Mar 2026 23:44:57 +0100 [thread overview]
Message-ID: <aaypYglgM4po78Kh@devuan> (raw)
In-Reply-To: <d3b5a021-9299-466c-b939-c54143034e86@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Hi Paul,
On 2026-03-07T12:59:10-0800, Paul Eggert wrote:
> On 2026-03-07 06:56, Alejandro Colomar wrote:
> > BTW, Paul, would you mind reviewing this bug report and suggestion?
>
> Although it's a start, we should add more detail about TAI and leap seconds,
> and the neighboring area could use some cleanup too. Proposed patch
> attached.
Thanks a lot! I've split the patch into several atomic patches,
minimally amended, and pushed.
51a4b682 (2026-03-07; "man/man2/clock_getres.2: CLOCK_TAI: Modernize leap-seconds documentation")
ffcf7de8 (2026-03-07; "man/man2/clock_getres.2: Clarify what "TAI" stands for.")
0676ddff (2026-03-07; "man/man2/clock_getres.2: wfix")
78a707b1 (2026-03-07; "man/man2/clock_getres.2: Some clocks behave differently if the system is suspended")
47e30f8e (2026-03-07; "man/man2/clock_getres.2: Clarify when clocks are indirectly settable")
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-07 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 14:21 [Bug 221186] New: clock_gettime CLOCK_TAI is incorrectly specified bugzilla-daemon
2026-03-07 14:56 ` Alejandro Colomar
2026-03-07 20:59 ` Paul Eggert
2026-03-07 22:44 ` Alejandro Colomar [this message]
2026-03-07 14:56 ` [Bug 221186] " bugzilla-daemon
2026-03-07 20:59 ` bugzilla-daemon
2026-03-07 22:45 ` bugzilla-daemon
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=aaypYglgM4po78Kh@devuan \
--to=alx@kernel.org \
--cc=bugzilla-daemon@kernel.org \
--cc=eggert@cs.ucla.edu \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.