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] tailq.3: fork from queue.3
Date: Sun, 25 Oct 2020 10:36:42 +0100 [thread overview]
Message-ID: <20201025093651.4616-1-colomar.6.4.3@gmail.com> (raw)
Hi Michael,
The last page is here :)
Cheers,
Alex
Alejandro Colomar (10):
tailq.3: New page that will hold the (tailq) contents of queue.3
queue.3, tailq.3: NAME: Move code from queue.3 to tailq.3
queue.3, tailq.3: SYNOPSIS: Move code from queue.3 to tailq.3
queue.3, tailq.3: DESCRIPTION: Move code from queue.3 to tailq.3
queue.3, tailq.3: EXAMPLES: Move code from queue.3 to tailq.3
tailq.3: Copy and adapt code from queue.3
tailq.3: ffix: Use man markup
tailq.3: Add remaining details to complete the page
TAILQ_CONCAT.3, TAILQ_EMPTY.3, TAILQ_ENTRY.3, TAILQ_FIRST.3,
TAILQ_FOREACH.3, TAILQ_FOREACH_REVERSE.3, TAILQ_HEAD.3,
TAILQ_HEAD_INITIALIZER.3, TAILQ_INIT.3, TAILQ_INSERT_AFTER.3,
TAILQ_INSERT_BEFORE.3, TAILQ_INSERT_HEAD.3, TAILQ_INSERT_TAIL.3,
TAILQ_LAST.3, TAILQ_NEXT.3, TAILQ_PREV.3, TAILQ_REMOVE.3,
TAILQ_SWAP.3: Link to the new tailq(3) page instead of queue(3)
queue.3: SEE ALSO: Add tailq(3)
man3/TAILQ_CONCAT.3 | 2 +-
man3/TAILQ_EMPTY.3 | 2 +-
man3/TAILQ_ENTRY.3 | 2 +-
man3/TAILQ_FIRST.3 | 2 +-
man3/TAILQ_FOREACH.3 | 2 +-
man3/TAILQ_FOREACH_REVERSE.3 | 2 +-
man3/TAILQ_HEAD.3 | 2 +-
man3/TAILQ_HEAD_INITIALIZER.3 | 2 +-
man3/TAILQ_INIT.3 | 2 +-
man3/TAILQ_INSERT_AFTER.3 | 2 +-
man3/TAILQ_INSERT_BEFORE.3 | 2 +-
man3/TAILQ_INSERT_HEAD.3 | 2 +-
man3/TAILQ_INSERT_TAIL.3 | 2 +-
man3/TAILQ_LAST.3 | 2 +-
man3/TAILQ_NEXT.3 | 2 +-
man3/TAILQ_PREV.3 | 2 +-
man3/TAILQ_REMOVE.3 | 2 +-
man3/TAILQ_SWAP.3 | 2 +-
man3/queue.3 | 343 +-------------------------
man3/tailq.3 | 437 ++++++++++++++++++++++++++++++++++
20 files changed, 456 insertions(+), 360 deletions(-)
create mode 100644 man3/tailq.3
--
2.28.0
next reply other threads:[~2020-10-25 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 9:36 Alejandro Colomar [this message]
2020-10-25 9:36 ` [PATCH 01/10] tailq.3: New page that will hold the (tailq) contents of queue.3 Alejandro Colomar
2020-10-25 9:36 ` [PATCH 02/10] queue.3, tailq.3: NAME: Move code from queue.3 to tailq.3 Alejandro Colomar
2020-10-25 9:36 ` [PATCH 03/10] queue.3, tailq.3: SYNOPSIS: " Alejandro Colomar
2020-10-25 9:36 ` [PATCH 04/10] queue.3, tailq.3: DESCRIPTION: " Alejandro Colomar
2020-10-25 9:36 ` [PATCH 05/10] queue.3, tailq.3: EXAMPLES: " Alejandro Colomar
2020-10-25 9:36 ` [PATCH 06/10] tailq.3: Copy and adapt code from queue.3 Alejandro Colomar
2020-10-25 9:36 ` [PATCH 07/10] tailq.3: ffix: Use man markup Alejandro Colomar
2020-10-25 9:36 ` [PATCH 08/10] tailq.3: Add remaining details to complete the page Alejandro Colomar
2020-10-25 9:36 ` [PATCH 09/10] TAILQ_CONCAT.3, TAILQ_EMPTY.3, TAILQ_ENTRY.3, TAILQ_FIRST.3, TAILQ_FOREACH.3, TAILQ_FOREACH_REVERSE.3, TAILQ_HEAD.3, TAILQ_HEAD_INITIALIZER.3, TAILQ_INIT.3, TAILQ_INSERT_AFTER.3, TAILQ_INSERT_BEFORE.3, TAILQ_INSERT_HEAD.3, TAILQ_INSERT_TAIL.3, TAILQ_LAST.3, TAILQ_NEXT.3, TAILQ_PREV.3, TAILQ_REMOVE.3, TAILQ_SWAP.3: Link to the new tailq(3) page instead of queue(3) Alejandro Colomar
2020-10-25 9:36 ` [PATCH 10/10] queue.3: SEE ALSO: Add tailq(3) Alejandro Colomar
2020-10-25 9:46 ` [PATCH 00/10] tailq.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=20201025093651.4616-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).