From: Alejandro Colomar <alx.manpages@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: linux-man@vger.kernel.org, groff@gnu.org,
g.branden.robinson@gmail.com,
Ralph Corderoy <ralph@inputplus.co.uk>
Subject: Re: [PATCH v3] NULL.3const: Add documentation for NULL
Date: Fri, 29 Jul 2022 01:28:31 +0200 [thread overview]
Message-ID: <94e9eedb-d2c8-4b89-08bb-007bca6b9d5c@gmail.com> (raw)
In-Reply-To: <36ff0943-4766-e933-012a-82c9ad611791@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1798 bytes --]
Hi Ingo,
On 7/27/22 15:11, Alejandro Colomar wrote:
>>>>> +.SH CONFORMING TO
>>
>>>> That should be ".SH STANDARDS".
>>
>>> We use CONFORMING TO in Linux. Don't know why; just history, I guess.
>>> See man-pages(7).
>>
>> Weird.
>>
>> I failed to find a single instance of "CONFORMING TO" in AT&T UNIX
>> (including v6, PWB, v7, 32v, v8, v10, System III, SVR1, SVR2) nor in
>> any version of UCB CSRG BSD. So considering that System V and BSD are
>> widely considered the two main original branches of the development
>> of Unix-like operating systems and Linux is often considered to have
>> drawn inspiration from both, the section name "CONFORMING TO" does
>> not appear to be a UNIX thing. For example, Aeleen Frisch, "Essential
>> System Administration", O'Reilly, Cambridge 1995, considers Linux
>> as slightly more influenced by 4.3BSD than by System V Release 3.
>>
>> STANDARDS, on the other hand, is present since 4.3BSD-Reno (June 1990).
>>
>> 4.3BSD-Reno predates the first version of the Linux kernel by more than
>> a year, and the first Linux manual pages probably for longer than that.
>>
>> So i have no idea where "CONFORMING TO" may have come from.
>
> I don't like the idea of being inconsistent with other Unix systems with
> no good reason. 's/CONFORMING TO/STANDARDS/' might happen some day;
> just saying.
I've already changed that. I didn't yet push to <kernel.org>. The
patch is in my server, for you to check:
<http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?id=8aac6f8f512e46a008140b93956b6c414ab13a04>.
It didn't fit in an email (the mailing list is limited to 100KB).
I'll probably push tomorrow.
Cheers,
Alex
--
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-28 23:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 15:31 [PATCH] NULL.3def: Add documentation for NULL Alejandro Colomar
2022-07-23 10:23 ` Ralph Corderoy
2022-07-24 12:49 ` Alejandro Colomar (man-pages)
2022-07-24 18:36 ` [PATCH] NULL.3const: " Alejandro Colomar
2022-07-24 19:19 ` [PATCH v3] " Alejandro Colomar
2022-07-25 18:49 ` Ingo Schwarze
2022-07-26 12:02 ` Alejandro Colomar
2022-07-27 10:49 ` Ingo Schwarze
2022-07-27 13:11 ` Alejandro Colomar
2022-07-28 23:28 ` Alejandro Colomar [this message]
2022-07-25 18:57 ` Jakub Wilk
2022-07-26 12:36 ` Alejandro Colomar
2022-07-26 12:48 ` [PATCH v4] " Alejandro Colomar
2022-07-26 15:54 ` G. Branden Robinson
2022-07-26 18:47 ` Alejandro Colomar
2022-07-27 9:50 ` Ingo Schwarze
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=94e9eedb-d2c8-4b89-08bb-007bca6b9d5c@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=linux-man@vger.kernel.org \
--cc=ralph@inputplus.co.uk \
--cc=schwarze@usta.de \
/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