From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 2/3] man/man3/getenv.3: Mention secure_getenv was standardized in POSIX-1.2024
Date: Sat, 17 May 2025 14:25:41 -0700 [thread overview]
Message-ID: <87v7pznd4a.fsf@gmail.com> (raw)
In-Reply-To: <ationx4kn5f2d5b76ayyufnjakuy5q3pkgmgq7fagwgakfitar@5l6ty5ftdsrg>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
Alejandro Colomar <alx@kernel.org> writes:
> In HISTORY, I tend to not remove any details about versions. The glibc
> version where it was introduced might be useful for someone, so let's
> keep it. Other than that, LGTM. Thanks!
I thought the same, but I based my patch on getline which was GNU before
POSIX. It has:
GNU, POSIX.1-2008.
What would it be better to do:
glibc 2.17, POSIX.1-2024
or should it be:
GNU (glibc 2.17), POSIX.1-2024
I would check other examples, but my memory for other functions POSIX
adopted from GNU isn't working well...
Collin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2025-05-17 21:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:53 [PATCH 1/3] man/man7/signal.7: Mention SIGWINCH was standardized in POSIX-1.2024 Collin Funk
2025-05-17 20:53 ` [PATCH 2/3] man/man3/getenv.3: Mention secure_getenv " Collin Funk
2025-05-17 21:17 ` Alejandro Colomar
2025-05-17 21:25 ` Collin Funk [this message]
2025-05-17 21:34 ` Alejandro Colomar
2025-05-17 22:19 ` Collin Funk
2025-05-18 7:58 ` Alejandro Colomar
2025-05-23 3:18 ` Collin Funk
2025-05-23 10:07 ` Alejandro Colomar
2025-05-23 21:22 ` Collin Funk
2025-05-24 17:46 ` Alejandro Colomar
2025-05-17 20:53 ` [PATCH 3/3] man/man3/ptsname.3: Mention ptsname_r " Collin Funk
2025-05-17 21:20 ` Alejandro Colomar
2025-05-17 21:16 ` [PATCH 1/3] man/man7/signal.7: Mention SIGWINCH " Alejandro Colomar
2025-05-17 21:43 ` the correct way to say "POSIX 2024" G. Branden Robinson
2025-05-17 22:40 ` Mark Harris
2025-05-17 22:45 ` G. Branden Robinson
2025-05-18 7:12 ` Alejandro Colomar
2025-05-18 7:52 ` Alejandro Colomar
2025-05-17 22:10 ` [PATCH v2 1/2] man/man7/signal.7: Mention SIGWINCH was standardized in POSIX-1.2024 Collin Funk
2025-05-17 22:10 ` [PATCH v2 2/2] man/man3/getenv.3: Mention secure_getenv " Collin Funk
2025-05-18 8:02 ` Alejandro Colomar
2025-05-18 8:00 ` [PATCH v2 1/2] man/man7/signal.7: Mention SIGWINCH " 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=87v7pznd4a.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=alx@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox