From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 3/4] tm.3type: describe tm_zone, tm_gmtoff
Date: Tue, 19 Jul 2022 19:11:29 +0200 [thread overview]
Message-ID: <1827b181-9541-eb67-7ca5-dc385a5e73d3@gmail.com> (raw)
In-Reply-To: <79b8858b80acc770138afc505eecc08f90ea1be6.1658244821.git.nabijaczleweli@nabijaczleweli.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1320 bytes --]
On 7/19/22 17:35, наб wrote:
> ---
> man3/tm.3type | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/man3/tm.3type b/man3/tm.3type
> index 78e05a41a..e7e39cc5c 100644
> --- a/man3/tm.3type
> +++ b/man3/tm.3type
[...]
> @@ -48,10 +76,30 @@ in C99.
> .SH CONFORMING TO
> C90 and later;
> POSIX.1-2001 and later.
> +.PP
> +.IR tm_gmtoff " and " tm_zone
I prefer one identifier per line:
.I foo
and
.I bar
> +originate from 4.3BSD-Tahoe (where
> +.I tm_zone
> +is a
> +.IR "char *" ).
> .SH NOTES
> .I tm_sec
> can represent a leap second with the value
> .BR 60 .
> +.PP
> +.BR timezone (3),
> +as a variable, is an XSI extension: some systems provide the V7-compatible
> +.\" FreeBSD
> +.BR timezone ()
> +function.
> +The
> +.I tm_gmtoff
> +field provides an alternative (with the opposite sign) for those systems.
> +.PP
> +.I tm_zone
> +points to static storage and may be overriden on subsequent calls to
> +.BR localtime (3)
> +and similar functions (this, however, never happens under glibc).
If you reorder it, you can remove a coma:
however, this never ...
> .SH SEE ALSO
> .BR ctime (3),
> .BR strftime (3),
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-19 17:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 1:56 [PATCH 1/5] tm.3type: tfix наб
2022-07-19 1:56 ` [PATCH 2/5] tm.3type: align ranges наб
2022-07-19 11:44 ` Alejandro Colomar
2022-07-19 14:14 ` наб
2022-07-19 14:25 ` Alejandro Colomar
2022-07-19 1:56 ` [PATCH 3/5] tm.3type: tm_year is year minus 1900, not since наб
2022-07-19 11:47 ` Alejandro Colomar
2022-07-19 11:50 ` Alejandro Colomar
2022-07-19 1:56 ` [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff наб
2022-07-19 12:17 ` Alejandro Colomar
2022-07-19 12:19 ` Alejandro Colomar
2022-07-19 15:28 ` наб
2022-07-22 3:33 ` G. Branden Robinson
2022-07-22 10:57 ` Alejandro Colomar (man-pages)
2022-07-22 22:20 ` man(7) DS and DE macros (was: [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff) G. Branden Robinson
2022-07-22 23:47 ` Alejandro Colomar
2025-10-29 9:07 ` [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff G. Branden Robinson
2025-10-29 10:21 ` Alejandro Colomar
2025-10-29 22:30 ` G. Branden Robinson
2025-10-29 22:53 ` Alejandro Colomar
2022-07-19 1:58 ` [PATCH 5/5] ctime.3: remove struct tm vestigia наб
2022-07-19 12:18 ` Alejandro Colomar
2022-07-19 11:38 ` [PATCH 1/5] tm.3type: tfix Alejandro Colomar
2022-07-19 15:35 ` [PATCH v2 1/4] tm.3type: align ranges наб
2022-07-19 18:38 ` [PATCH v3 1/2] tm.3type: describe tm_zone, tm_gmtoff наб
2022-07-19 20:33 ` Alejandro Colomar
2022-07-19 21:36 ` наб
2022-07-19 22:09 ` Alejandro Colomar
2022-07-19 22:35 ` [PATCH v4 " наб
2022-07-19 22:36 ` [PATCH v4 2/2] ctime.3: remove struct tm vestigia наб
2022-07-20 8:30 ` Alejandro Colomar
2022-07-19 18:39 ` [PATCH v3 " наб
2022-07-19 15:35 ` [PATCH v2 2/4] tm.3type: widen member alignment to take up to const char * наб
2022-07-19 15:59 ` Alejandro Colomar
2022-07-19 15:35 ` [PATCH v2 3/4] tm.3type: describe tm_zone, tm_gmtoff наб
2022-07-19 17:11 ` Alejandro Colomar [this message]
2022-07-19 15:35 ` [PATCH v2 4/4] ctime.3: remove struct tm vestigia наб
2022-07-19 17:12 ` 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=1827b181-9541-eb67-7ca5-dc385a5e73d3@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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.