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 00/11] man3: fix wrong/non-existent section references
Date: Sat, 15 Jun 2024 18:18:53 -0700	[thread overview]
Message-ID: <20240616011920.1627949-1-kolyshkin@gmail.com> (raw)

Commit 4131356cd ("man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY:
Reorganize sections") results in many wrong section references.

Mostly, this is about references to no-longer-existent section NOTES,
but there are some other issues as well, such as references to a wrong
section, or a discussion which is now split in between two sections,
etc.

This patch series tries to fix some of these issues in man3 section
only (I haven't checked other section numbers).

Found accidentally when reading exec(3).

Kir Kolyshkin (11):
  exec.3: fix section reference
  posix_fallocate.3: fix section references
  floor.3: fix section reference
  ceil.3,rint.3,round.3: rm NOTES section
  getdtablesize.3: fix section reference
  readdir.3: fix section references
  setjmp.3: fix section references
  sigpause.3: fix section reference
  stailq.3: fix section reference
  strtok.3: fix section reference
  strtod.3: fix wrong section reference

 man/man3/ceil.3            | 4 ++--
 man/man3/exec.3            | 2 +-
 man/man3/floor.3           | 2 +-
 man/man3/getdtablesize.3   | 2 +-
 man/man3/posix_fallocate.3 | 4 ++--
 man/man3/readdir.3         | 8 ++++----
 man/man3/rint.3            | 4 ++--
 man/man3/round.3           | 4 ++--
 man/man3/setjmp.3          | 6 +++---
 man/man3/sigpause.3        | 2 +-
 man/man3/stailq.3          | 2 +-
 man/man3/strtod.3          | 2 +-
 man/man3/strtok.3          | 2 +-
 13 files changed, 22 insertions(+), 22 deletions(-)

-- 
2.45.2


             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 Kir Kolyshkin [this message]
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 ` [PATCH 07/11] setjmp.3: fix " Kir Kolyshkin
2024-06-16 10:47   ` 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-1-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