Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 1/3] queue.3, queue.7: Move queue.3 to queue.7
Date: Sun, 25 Oct 2020 21:46:16 +0100	[thread overview]
Message-ID: <20201025204617.6802-2-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20201025204617.6802-1-colomar.6.4.3@gmail.com>

After forking slist.3, list.3, tailq.3, stailq.3 & circleq.3
in the previous commits,
this page no longer belongs in Section 3 of the manual pages.

According to its contents, the most suitable section is Section 7.

Because of legacy reasons, a link queue.3 -> queue(7)
would be appropriate.

Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
 man3/queue.3 => man7/queue.7 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename man3/queue.3 => man7/queue.7 (98%)

diff --git a/man3/queue.3 b/man7/queue.7
similarity index 98%
rename from man3/queue.3
rename to man7/queue.7
index cbe72e29d..1fe48bd57 100644
--- a/man3/queue.3
+++ b/man7/queue.7
@@ -29,7 +29,7 @@
 .\" %%%LICENSE_END
 .\"
 .\"
-.TH QUEUE 3 2015-02-7 "GNU" "Linux Programmer's Manual"
+.TH QUEUE 7 2015-02-7 "GNU" "Linux Programmer's Manual"
 .SH NAME
 queue \- implementations of linked lists and queues
 .SH DESCRIPTION
-- 
2.28.0


  reply	other threads:[~2020-10-25 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 20:46 [PATCH 0/3] Move queue.3 to queue.7 Alejandro Colomar
2020-10-25 20:46 ` Alejandro Colomar [this message]
2020-10-25 20:46 ` [PATCH 2/3] queue.3: Link to queue(7) Alejandro Colomar
2020-10-25 20:46 ` [PATCH 3/3] circleq.3, insque.3, list.3, slist.3, tailq.3: SEE ALSO: queue(3) -> queue(7) Alejandro Colomar
2020-10-25 21:19 ` [PATCH 0/3] Move queue.3 to queue.7 Michael Kerrisk (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=20201025204617.6802-2-colomar.6.4.3@gmail.com \
    --to=colomar.6.4.3@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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