From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] putenv.3: originated in SysVr2; in 4.3BSD-Reno; fixed on modern systems
Date: Tue, 23 May 2023 22:58:42 +0200 [thread overview]
Message-ID: <5qegumqc3s7pvtrwfffyajhaxmv76kmhubz4bawcku3hap7dso@apgctax4wzln> (raw)
In-Reply-To: <389e9350-cb85-9a21-4a06-56344b7057e8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On Tue, May 23, 2023 at 10:20:07PM +0200, Alejandro Colomar wrote:
> On 5/23/23 22:17, наб wrote:
> > @@ -119,7 +119,8 @@ .SH HISTORY
> > On the one hand this causes a memory leak, and on the other hand
> > it violates SUSv2.
> > .PP
> > -The 4.4BSD version, like glibc 2.0, uses a copy.
> > +The 4.3BSD-Reno version, like glibc 2.0, uses a copy;
> Maybe we should say s/uses/used/?
4.3BSD-Reno is a single release and hence a single version,
and nothing's changed about it, so it still "is".
We could say "The BSD used" but we have hard versions, so.
The same holds for the first long line in HISTORY:
The putenv() function is not required to be reentrant, and the one in
glibc 2.0 is not, but the glibc 2.1 version is.
the singular version which was part of the glibc 2.0 release(s) hasn't
changed in glibc 2.0, and glibc 2.0 "is" (but yeah, glibc "was").
Present tense also appears to be a prevalent style globally:
setuid(2) says "Not quite compatible with the 4.4BSD call, which sets
all of the real, saved, and effective user IDs."
setjmp(3) says "In 4.3BSD it will, and there is a function _setjmp()
that will not."
Best,
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-23 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 20:17 [PATCH] putenv.3: originated in SysVr2; in 4.3BSD-Reno; fixed on modern systems наб
2023-05-23 20:20 ` Alejandro Colomar
2023-05-23 20:58 ` наб [this message]
2023-05-23 23:20 ` 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=5qegumqc3s7pvtrwfffyajhaxmv76kmhubz4bawcku3hap7dso@apgctax4wzln \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=alx.manpages@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).