public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Kir Kolyshkin <kolyshkin@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Kir Kolyshkin <kolyshkin@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 07/11] setjmp.3: fix section references
Date: Sat, 15 Jun 2024 18:19:00 -0700	[thread overview]
Message-ID: <20240616011920.1627949-8-kolyshkin@gmail.com> (raw)
In-Reply-To: <20240616011920.1627949-1-kolyshkin@gmail.com>

Commit 4131356cd ("man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY:
Reorganize sections") results in a few problems with setjmp(3):

 1. "Feature Test Macro Requirements for glibc" refers to NOTES, while
    those macros are now described in HISTORY.

 2. The discussion about saving signal mask is now split between HISTORY
    and NOTES.

To fix all this, let's remove NOTES and fix references to point to
HISTORY.

Fixes: 4131356cd
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
 man/man3/setjmp.3 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man/man3/setjmp.3 b/man/man3/setjmp.3
index 2319feb47..1403d6ba7 100644
--- a/man/man3/setjmp.3
+++ b/man/man3/setjmp.3
@@ -26,7 +26,7 @@ .SH SYNOPSIS
 .RE
 .P
 .BR setjmp ():
-see NOTES.
+see HISTORY.
 .P
 .BR sigsetjmp ():
 .nf
@@ -65,7 +65,7 @@ .SH DESCRIPTION
 was called and to restore ("rewind") the stack to its state at the time of the
 .BR setjmp ()
 call.
-In addition, and depending on the implementation (see NOTES),
+In addition, and depending on the implementation (see HISTORY),
 the values of some other registers and the process signal mask
 may be restored to their state at the time of the
 .BR setjmp ()
@@ -201,7 +201,7 @@ .SH HISTORY
 with a nonzero
 .I savesigs
 argument.
-.SH NOTES
+.P
 .BR setjmp ()
 and
 .BR longjmp ()
-- 
2.45.2


  parent reply	other threads:[~2024-06-16  1:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16  1:18 [PATCH 00/11] man3: fix wrong/non-existent section references Kir Kolyshkin
2024-06-16  1:18 ` [PATCH 01/11] exec.3: fix section reference Kir Kolyshkin
2024-06-16  1:18 ` [PATCH 02/11] posix_fallocate.3: fix section references Kir Kolyshkin
2024-06-16  1:18 ` [PATCH 03/11] floor.3: fix section reference Kir Kolyshkin
2024-06-16 10:07   ` Alejandro Colomar
2024-06-16  1:18 ` [PATCH 04/11] ceil.3,rint.3,round.3: rm NOTES section Kir Kolyshkin
2024-06-16  1:18 ` [PATCH 05/11] getdtablesize.3: fix section reference Kir Kolyshkin
2024-06-16  1:18 ` [PATCH 06/11] readdir.3: fix section references Kir Kolyshkin
2024-06-16 10:44   ` Alejandro Colomar
2024-06-16 20:13     ` [PATCH v2 06/11] readdir.3: fix wrong " Kir Kolyshkin
2024-06-16  1:19 ` Kir Kolyshkin [this message]
2024-06-16 10:47   ` [PATCH 07/11] setjmp.3: fix " Alejandro Colomar
2024-06-16 20:19     ` [PATCH v2 " Kir Kolyshkin
2024-06-16 20:43       ` Alejandro Colomar
2024-06-16  1:19 ` [PATCH 08/11] sigpause.3: fix section reference Kir Kolyshkin
2024-06-16  1:19 ` [PATCH 09/11] stailq.3: " Kir Kolyshkin
2024-06-16  1:19 ` [PATCH 10/11] strtok.3: " Kir Kolyshkin
2024-06-16  1:19 ` [PATCH 11/11] strtod.3: fix wrong " Kir Kolyshkin
2024-06-16 11:08 ` [PATCH 00/11] man3: fix wrong/non-existent section references 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=20240616011920.1627949-8-kolyshkin@gmail.com \
    --to=kolyshkin@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