From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH 0/6] man[23]: SYNOPSIS: Use 'noreturn' in prototypes.
Date: Thu, 18 Feb 2021 22:23:53 +0100 [thread overview]
Message-ID: <20210218212358.246072-1-alx.manpages@gmail.com> (raw)
Hi Michael,
Here's a patch for using 'noreturn' in the prototypes that never return,
such as exit(), abort(), longjmp(), etc, using standard C (C11) syntax.
This patch set fixes all of man2 and man3.
Cheers,
Alex
......
This was useful:
.../glibc$ man_lsfunc ../../linux/man-pages/man[23] \
|while read -r syscall; do
echo "============================= ${syscall}";
grep_glibc_prototype ${syscall} \
|sed -e 's/\bextern //' \
|pcregrep -M '(?s).*noreturn.*';
done \
|less;
---
Alejandro Colomar (6):
abort.3: SYNOPSIS: Use 'noreturn' in prototypes
_exit.2: SYNOPSIS: Use 'noreturn' in prototypes
err.3: SYNOPSIS: Use 'noreturn' in prototypes
exit.3: SYNOPSIS: Use 'noreturn' in prototypes
pthread_exit.3: SYNOPSIS: Use 'noreturn' in prototypes
setjmp.3: SYNOPSIS: Use 'noreturn' in prototypes
man2/_exit.2 | 4 ++--
man3/abort.3 | 2 +-
man3/err.3 | 8 ++++----
man3/exit.3 | 2 +-
man3/pthread_exit.3 | 2 +-
man3/setjmp.3 | 4 ++--
6 files changed, 11 insertions(+), 11 deletions(-)
--
2.30.1.721.g45526154a5
next reply other threads:[~2021-02-18 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 21:23 Alejandro Colomar [this message]
2021-02-18 21:23 ` [PATCH 1/6] abort.3: SYNOPSIS: Use 'noreturn' in prototypes Alejandro Colomar
2021-02-19 12:31 ` Michael Kerrisk (man-pages)
2021-02-18 21:23 ` [PATCH 2/6] _exit.2: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 3/6] err.3: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 4/6] exit.3: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 5/6] pthread_exit.3: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 6/6] setjmp.3: " 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=20210218212358.246072-1-alx.manpages@gmail.com \
--to=alx.manpages@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