public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Sam James <sam@gentoo.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] time_t.3type: reference _TIME_BITS
Date: Thu, 13 Oct 2022 15:08:01 +0200	[thread overview]
Message-ID: <0f177941-d432-516d-7610-bd38dd30c9f5@gmail.com> (raw)
In-Reply-To: <20221013003313.1809731-1-sam@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]

Hi Sam,

On 10/13/22 02:33, Sam James wrote:
> Just like we do with _FILE_OFFSET_BITS in off_t.3type.
> 
> Reference: https://wiki.gentoo.org/wiki/Project:Toolchain/time64_migration
> Reference: https://sourceware.org/pipermail/libc-alpha/2022-January/134985.html
> Signed-off-by: Sam James <sam@gentoo.org>

Looks good.  However, I see there's no documentation at all about 
_TIME_BITS in the man-pages.  Maybe you want to send a patch for ftm(7)?

Thanks!

Alex

> ---
>   man3type/time_t.3type | 6 ++++++
>   1 file changed, 6 insertions(+)
> 
> diff --git a/man3type/time_t.3type b/man3type/time_t.3type
> index d40dd0c0d..9b8f07356 100644
> --- a/man3type/time_t.3type
> +++ b/man3type/time_t.3type
> @@ -70,6 +70,12 @@ POSIX.1-2001 and later.
>   POSIX.1-2001 and later.
>   .PD
>   .SH NOTES
> +On some architectures,
> +the width of
> +.I time_t
> +can be controlled with the feature test macro
> +.BR _TIME_BITS .
> +.PP
>   .TP
>   .I time_t
>   The following headers also provide

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

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

      reply	other threads:[~2022-10-13 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  0:33 [PATCH] time_t.3type: reference _TIME_BITS Sam James
2022-10-13 13:08 ` Alejandro Colomar [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=0f177941-d432-516d-7610-bd38dd30c9f5@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=sam@gentoo.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