public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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 15:19:22 -0700	[thread overview]
Message-ID: <87msbaop79.fsf@gmail.com> (raw)
In-Reply-To: <aqq7gag27u7kwnltq4zumzjk2wvlsevbevm5lkgr3m2x5rhowf@hdufz4pmli3q>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Hi Alejandro,

Alejandro Colomar <alx@kernel.org> writes:

> This is the better.  Actually, I tend to put POSIX before glibc:
>
> 	POSIX.1-2024, glibc 2.17.
>
> I'll check the existing pages to try to put a consistent order.  For new
> ones, let's do POSIX first (and ISO C before POSIX).

[...]

> I use glibc and version if I know the version, or just GNU if I don't
> know it.

Cool, that makes sense. Thanks for the details.

I sent a v2 of those 2 patches.

FYI, I left the documentation that ptsname_r returns -1 on Tru64 and
HP-UX. I just remembered that this is also the case on FreeBSD where I
reported it and it was documented 2 years ago [1]. But it still hasn't
been changed [2].

Do you think that is worth documenting? We have to work around this in
Gnulib, for example, so applications can be portable.

Collin

[1] https://github.com/freebsd/freebsd-src/commit/a5ed6a815e38d6c622cd97a6020592ded579cf7a
[2] https://github.com/freebsd/freebsd-src/blob/6b8222793fbb4c0e162232716bc454dad31b709f/lib/libc/stdlib/ptsname.c#L74

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2025-05-17 22:19 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
2025-05-17 21:34       ` Alejandro Colomar
2025-05-17 22:19         ` Collin Funk [this message]
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=87msbaop79.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