From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 5/5] ctime.3: remove struct tm vestigia
Date: Tue, 19 Jul 2022 14:18:35 +0200 [thread overview]
Message-ID: <306ec759-d0bf-fc23-9d23-4902c404eee6@gmail.com> (raw)
In-Reply-To: <36e71b9680341df1a27070b6446c20d562ecc3ba.1658195739.git.nabijaczleweli@nabijaczleweli.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1463 bytes --]
On 7/19/22 03:58, наб wrote:
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> Funnily enough, I noticed this only when writing the commit message for
> the previous patch and attempting to ascertain how much I should
> complain about what's in man-pages 5.10 (which has just tm_zone (!)),
> so that commit is entirely unrelated to this one, and its text is
> entirely unrelated to this page's
Ahh, I see that's here.
Maybe rewrite the previous commit message?
I'll hold applying this patch.
Thanks,
Alex
>
> man3/ctime.3 | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> diff --git a/man3/ctime.3 b/man3/ctime.3
> index d228bdc21..60ee4418d 100644
> --- a/man3/ctime.3
> +++ b/man3/ctime.3
> @@ -356,21 +356,6 @@ In many implementations, including glibc, a 0 in
> .I tm_mday
> is interpreted as meaning the last day of the preceding month.
> .PP
> -The glibc version of \fIstruct tm\fP has additional fields
> -.PP
> -.in +4n
> -.EX
> -long tm_gmtoff; /* Seconds east of UTC */
> -const char *tm_zone; /* Timezone abbreviation */
> -.EE
> -.in
> -.PP
> -defined when
> -.B _BSD_SOURCE
> -was set before including
> -.IR <time.h> .
> -This is a BSD extension, present in 4.3BSD-Reno.
> -.PP
> According to POSIX.1-2001,
> .BR localtime ()
> is required to behave as though
--
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 12:48 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 [this message]
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
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=306ec759-d0bf-fc23-9d23-4902c404eee6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox