From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Collin Funk <collin.funk1@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 2/3] man/man3/getenv.3: Mention secure_getenv was standardized in POSIX-1.2024
Date: Sat, 17 May 2025 13:53:03 -0700 [thread overview]
Message-ID: <f1cc4b34bb42b09ae9c0820df8fdece6fcebfcd8.1747515178.git.collin.funk1@gmail.com> (raw)
In-Reply-To: <6abbe99f5e8710202650bfee5d41e6fceaff4d1c.1747515178.git.collin.funk1@gmail.com>
Signed-off-by: Collin Funk <collin.funk1@gmail.com>
---
man/man3/getenv.3 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/man/man3/getenv.3 b/man/man3/getenv.3
index f05e3eda5..8285dfc21 100644
--- a/man/man3/getenv.3
+++ b/man/man3/getenv.3
@@ -36,7 +36,7 @@ .SH DESCRIPTION
.I value
string.
.P
-The GNU-specific
+The
.BR secure_getenv ()
function is just like
.BR getenv ()
@@ -88,14 +88,14 @@ .SH STANDARDS
C11, POSIX.1-2008.
.TP
.BR secure_getenv ()
-GNU.
+POSIX.1-2024.
.SH HISTORY
.TP
.BR getenv ()
POSIX.1-2001, C89, C99, SVr4, 4.3BSD.
.TP
.BR secure_getenv ()
-glibc 2.17.
+GNU.
.SH NOTES
The strings in the environment list are of the form
.IR name=value .
--
2.49.0
next prev parent reply other threads:[~2025-05-17 20:53 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 ` Collin Funk [this message]
2025-05-17 21:17 ` [PATCH 2/3] man/man3/getenv.3: Mention secure_getenv " Alejandro Colomar
2025-05-17 21:25 ` Collin Funk
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=f1cc4b34bb42b09ae9c0820df8fdece6fcebfcd8.1747515178.git.collin.funk1@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