From: Ingo Schwarze <schwarze@usta.de>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man-pages.7: Document CAVEATS section
Date: Tue, 26 Jul 2022 15:54:56 +0200 [thread overview]
Message-ID: <Yt/yMJuhXd+jH3sp@asta-kit.de> (raw)
In-Reply-To: <20220726120817.100462-1-alx.manpages@gmail.com>
Hi Alejandro,
Alejandro Colomar wrote on Tue, Jul 26, 2022 at 02:08:18PM +0200:
> CAVEATS is an interesting section from OpenBSD.
It is no doubt nice when credit is given to OpenBSD,
but in this case, it happens to be undeserved. ;-)
I see the following early uses of ".SH CAVEATS":
* 4.2BSD execve(2), released September 1983, author unknown
* 4.3BSD-Tahoe patch(1), released June 1988, author: Larry Wall
* 4.3BSD-Reno amd(8), released June 1990, author: Jan-Simon Pendry
* 4.4BSD strftime(3), released June 1993, author: Arnold Robbins
* 4.4BSD gzip(1), released June 1993, author (unsure) Jean-loup Gailly ?
* 4.4BSD mount_kernfs(8), released June 1993, author: Jan-Simon Pendry
The first instance of ".Sh CAVEATS" i found is:
* 4.4BSD-Lite1 realpath(3), released April 1994, author Keith Bostic
It doesn't look as if the UC CSRG used CAVEATS in additional files.
Standardization was decided in NetBSD during a discussion
on <tech-userlevel@netbsd.org> leading to this commit:
/src/share/misc/mdoc.template revision 1.6
date: 2002-07-10 09:45:18 +0000; author: yamt; state: Exp; lines: +2 -1;
add CAVEATS section. discussed on tech-userlevel.
The login name "yamt" belongs to YAMAMOTO Takashi.
It was then quickly picked up in OpenBSD by Jason McIntyre.
So the section has a tradition of almost 40 years and has been
standardized in *BSD for about two decades, even though it was
not originally a BSD invention.
Yours,
Ingo
next prev parent reply other threads:[~2022-07-26 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 12:08 [PATCH] man-pages.7: Document CAVEATS section Alejandro Colomar
2022-07-26 13:54 ` Ingo Schwarze [this message]
2022-07-26 14:29 ` Alejandro Colomar
2022-07-26 15:37 ` Ingo Schwarze
2022-07-26 19:02 ` Alejandro Colomar
2022-07-27 9:14 ` Ingo Schwarze
2022-07-27 9:23 ` Alejandro Colomar (man-pages)
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=Yt/yMJuhXd+jH3sp@asta-kit.de \
--to=schwarze@usta.de \
--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