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, libc-alpha@sourceware.org
Subject: [PATCH 02/10] queue.3, slist.3: NAME: Move code from queue.3 to slist.3
Date: Thu, 22 Oct 2020 14:38:14 +0200 [thread overview]
Message-ID: <20201022123821.22602-3-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20201022123821.22602-1-colomar.6.4.3@gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
man3/queue.3 | 17 -----------------
man3/slist.3 | 17 +++++++++++++++++
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/man3/queue.3 b/man3/queue.3
index 90fd3db0e..8fc10892a 100644
--- a/man3/queue.3
+++ b/man3/queue.3
@@ -34,23 +34,6 @@
.Dt QUEUE 3
.Os
.Sh NAME
-.Nm SLIST_EMPTY ,
-.Nm SLIST_ENTRY ,
-.Nm SLIST_FIRST ,
-.Nm SLIST_FOREACH ,
-.\" .Nm SLIST_FOREACH_FROM ,
-.\" .Nm SLIST_FOREACH_SAFE ,
-.\" .Nm SLIST_FOREACH_FROM_SAFE ,
-.Nm SLIST_HEAD ,
-.Nm SLIST_HEAD_INITIALIZER ,
-.Nm SLIST_INIT ,
-.Nm SLIST_INSERT_AFTER ,
-.Nm SLIST_INSERT_HEAD ,
-.Nm SLIST_NEXT ,
-.\" .Nm SLIST_REMOVE_AFTER ,
-.Nm SLIST_REMOVE_HEAD ,
-.Nm SLIST_REMOVE ,
-.\" .Nm SLIST_SWAP ,
.Nm STAILQ_CONCAT ,
.Nm STAILQ_EMPTY ,
.Nm STAILQ_ENTRY ,
diff --git a/man3/slist.3 b/man3/slist.3
index 20058a9c6..d2f1fac66 100644
--- a/man3/slist.3
+++ b/man3/slist.3
@@ -31,6 +31,23 @@
.\"
.TH SLIST 3 2020-10-21 "GNU" "Linux Programmer's Manual"
.SH NAME
+.Nm SLIST_EMPTY ,
+.Nm SLIST_ENTRY ,
+.Nm SLIST_FIRST ,
+.Nm SLIST_FOREACH ,
+.\" .Nm SLIST_FOREACH_FROM ,
+.\" .Nm SLIST_FOREACH_SAFE ,
+.\" .Nm SLIST_FOREACH_FROM_SAFE ,
+.Nm SLIST_HEAD ,
+.Nm SLIST_HEAD_INITIALIZER ,
+.Nm SLIST_INIT ,
+.Nm SLIST_INSERT_AFTER ,
+.Nm SLIST_INSERT_HEAD ,
+.Nm SLIST_NEXT ,
+.\" .Nm SLIST_REMOVE_AFTER ,
+.Nm SLIST_REMOVE_HEAD ,
+.Nm SLIST_REMOVE ,
+.\" .Nm SLIST_SWAP ,
.SH SYNOPSIS
.SH DESCRIPTION
.SH RETURN VALUE
--
2.28.0
next prev parent reply other threads:[~2020-10-22 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:38 [PATCH 00/10] slist.3: fork from queue.3 Alejandro Colomar
2020-10-22 12:38 ` [PATCH 01/10] slist.3: New page that will hold the (slist) contents of queue.3 Alejandro Colomar
2020-10-22 12:38 ` Alejandro Colomar [this message]
2020-10-22 12:38 ` [PATCH 03/10] queue.3, slist.3: SYNOPSIS: Move code from queue.3 to list.3 Alejandro Colomar
2020-10-22 12:38 ` [PATCH 04/10] queue.3, slist.3: DESCRIPTION: Move slist specific code from queue.3 to slist.3 Alejandro Colomar
2020-10-22 12:38 ` [PATCH 05/10] queue.3, slist.3: EXAMPLES: Move example program " Alejandro Colomar
2020-10-22 12:38 ` [PATCH 06/10] slist.3: Copy and adapt code from queue.3 Alejandro Colomar
2020-10-22 12:38 ` [PATCH 07/10] slist.3: ffix: Use man markup Alejandro Colomar
2020-10-22 12:38 ` [PATCH 08/10] slist.3: Add details Alejandro Colomar
2020-10-22 12:38 ` [PATCH 09/10] SLIST_EMPTY.3, SLIST_ENTRY.3, SLIST_FIRST.3, SLIST_FOREACH.3, SLIST_HEAD.3, SLIST_HEAD_INITIALIZER.3, SLIST_INIT.3, SLIST_INSERT_AFTER.3, SLIST_INSERT_HEAD.3, SLIST_NEXT.3, SLIST_REMOVE.3, SLIST_REMOVE_HEAD.3: Link to the new slist(3) page instead of queue(3) Alejandro Colomar
2020-10-22 12:38 ` [PATCH 10/10] queue.3: SEE ALSO: Add slist(3) Alejandro Colomar
2020-10-22 17:48 ` [PATCH 00/10] slist.3: fork from queue.3 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=20201022123821.22602-3-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.org \
--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;
as well as URLs for NNTP newsgroup(s).