All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man-pages.7: Document CAVEATS section
Date: Tue, 26 Jul 2022 16:29:49 +0200	[thread overview]
Message-ID: <7effe1a8-c1b4-5542-932a-7edf436036ce@gmail.com> (raw)
In-Reply-To: <Yt/yMJuhXd+jH3sp@asta-kit.de>


[-- Attachment #1.1: Type: text/plain, Size: 1837 bytes --]

Hi Ingo,

On 7/26/22 15:54, Ingo Schwarze wrote:
> 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.

Wasn't it a BSD invention?  The sources you mentioned seem to say it is.

Would it be correct to say "... section from the BSDs"?

Cheers,

Alex

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-07-26 14:30 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
2022-07-26 14:29   ` Alejandro Colomar [this message]
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=7effe1a8-c1b4-5542-932a-7edf436036ce@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.