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 00/10] slist.3: fork from queue.3
Date: Thu, 22 Oct 2020 14:38:12 +0200 [thread overview]
Message-ID: <20201022123821.22602-1-colomar.6.4.3@gmail.com> (raw)
Hi Michael,
Here's slist.3.
I applied to this page all of the fixes you applied to list.3.
Also I noticed some unsorted macros,
so I'll check list.3 and sort them if necessary.
Cheers,
Alex
Alejandro Colomar (10):
slist.3: New page that will hold the (slist) contents of queue.3
queue.3, slist.3: NAME: Move code from queue.3 to slist.3
queue.3, slist.3: SYNOPSIS: Move code from queue.3 to list.3
queue.3, slist.3: DESCRIPTION: Move slist specific code from queue.3
to slist.3
queue.3, slist.3: EXAMPLES: Move example program from queue.3 to
slist.3
slist.3: Copy and adapt code from queue.3
slist.3: ffix: Use man markup
slist.3: Add details
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)
queue.3: SEE ALSO: Add slist(3)
man3/SLIST_EMPTY.3 | 2 +-
man3/SLIST_ENTRY.3 | 2 +-
man3/SLIST_FIRST.3 | 2 +-
man3/SLIST_FOREACH.3 | 2 +-
man3/SLIST_HEAD.3 | 2 +-
man3/SLIST_HEAD_INITIALIZER.3 | 2 +-
man3/SLIST_INIT.3 | 2 +-
man3/SLIST_INSERT_AFTER.3 | 2 +-
man3/SLIST_INSERT_HEAD.3 | 2 +-
man3/SLIST_NEXT.3 | 2 +-
man3/SLIST_REMOVE.3 | 2 +-
man3/SLIST_REMOVE_HEAD.3 | 2 +-
man3/queue.3 | 248 +-----------------------
man3/slist.3 | 355 ++++++++++++++++++++++++++++++++++
14 files changed, 368 insertions(+), 259 deletions(-)
create mode 100644 man3/slist.3
--
2.28.0
next reply other threads:[~2020-10-22 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:38 Alejandro Colomar [this message]
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 ` [PATCH 02/10] queue.3, slist.3: NAME: Move code from queue.3 to slist.3 Alejandro Colomar
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-1-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 read-only IMAP folder(s) and NNTP newsgroup(s).