public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Mark Harris <mark.hsj@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 1/2] man/man3/timespec_get.3: Refactor to prepare for new time bases
Date: Thu, 29 Jan 2026 16:28:29 +0100	[thread overview]
Message-ID: <aXt76inr6vGh4lod@devuan> (raw)
In-Reply-To: <79f235d4b360689a290d525c36c3a06a36e5164a.1769619403.git.mark.hsj@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi Mark,

On 2026-01-28T09:33:03-0800, Mark Harris wrote:
> Add Feature Test Macro Requirements to document functions and macros
> that require ISO C11 or C23, and arrange supported time bases as a list.
> 
> Signed-off-by: Mark Harris <mark.hsj@gmail.com>
> ---
> v2: Split into two patches, add time bases to History section
> 
>  man/man3/timespec_get.3 | 32 ++++++++++++++++++++++++--------
>  1 file changed, 24 insertions(+), 8 deletions(-)

[...]
> @@ -78,18 +96,16 @@ .SH ATTRIBUTES
>  .SH STANDARDS
>  .TP
>  .BR timespec_get ()
> -.TQ
> +C23 (though ISO C doesn't specify the
>  .B TIME_UTC
> -C23 (though ISO C doesn't specify the time epoch),
> +epoch),
>  POSIX.1-2024.

How about this?:

	.TP
	.BR timespec_get ()
	C23, POSIX.1-2024.
	.TQ
	.B TIME_UTC
	C23 (though ISO C doesn't specify the time epoch),
	POSIX.1-2024.

>  .TP
>  .BR timespec_getres ()
>  C23.
>  .SH HISTORY
>  .TP
> -.BR timespec_get ()
> -.TQ
> -.B TIME_UTC
> +.BR timespec_get "(), " TIME_UTC

I prefer the format with TQ.  I wouldn't change anything in HISTORY.


Have a lovely day!
Alex

>  C11, POSIX.1-2024, glibc 2.16, musl 1.1.10.
>  .TP
>  .BR timespec_getres ()
> -- 
> 2.52.0
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-01-29 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28  6:42 [PATCH] man/man3/timespec_get.3: Add ISO C23 time bases Mark Harris
2026-01-28 14:57 ` Alejandro Colomar
2026-01-28 17:35   ` Mark Harris
2026-01-28 17:33 ` [PATCH v2 1/2] man/man3/timespec_get.3: Refactor to prepare for new " Mark Harris
2026-01-28 17:33   ` [PATCH v2 2/2] man/man3/timespec_get.3: Add ISO C23 " Mark Harris
2026-01-29 15:28   ` Alejandro Colomar [this message]
2026-01-29 16:58     ` [PATCH v2 1/2] man/man3/timespec_get.3: Refactor to prepare for new " Mark Harris
2026-01-29 16:52 ` [PATCH v3 " Mark Harris
2026-01-29 16:52   ` [PATCH v3 2/2] man/man3/timespec_get.3: Add ISO C23 " Mark Harris
2026-02-10 23:01     ` Alejandro Colomar
2026-02-10 22:53   ` [PATCH v3 1/2] man/man3/timespec_get.3: Refactor to prepare for new " Alejandro Colomar

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=aXt76inr6vGh4lod@devuan \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mark.hsj@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