From: Paul Eggert <eggert@cs.ucla.edu>
To: linux-man@vger.kernel.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH 0/4] improvements for strncpy.3 etc
Date: Sun, 12 Nov 2023 15:52:04 -0800 [thread overview]
Message-ID: <20231112235218.80195-1-eggert@cs.ucla.edu> (raw)
Improve man pages for strncpy and related functions.
Do this partly by using clearer terminology (e.g.,
"byte" rather than "character" which is ambiguous),
partly by being clearer about whether arguments need
to be strings, and partly by using better sample
implementations and examples.
This patch does not affect man pages for the corresponding
wide-character functions. These functions are rarely used
and so are lower priority.
It also does not affect string_copying(7) which needs similar
work; I ran out of time for now.
Paul Eggert (4):
* Remove man3/stpecpyx.3; no longer present.
string.3 fixes
strncat.3 fixes
stpncpy(3) fixes
man3/stpecpyx.3 | 1 -
man3/stpncpy.3 | 82 ++++++++++++++++++++++++-------------------------
man3/string.3 | 4 +--
man3/strncat.3 | 54 ++++++++++++++------------------
4 files changed, 65 insertions(+), 76 deletions(-)
delete mode 100644 man3/stpecpyx.3
--
2.41.0
next reply other threads:[~2023-11-12 23:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 23:52 Paul Eggert [this message]
2023-11-12 23:52 ` [PATCH 1/4] * Remove man3/stpecpyx.3; no longer present Paul Eggert
2023-11-13 0:18 ` Alejandro Colomar
2023-11-12 23:52 ` [PATCH 2/4] string.3 fixes Paul Eggert
2023-11-13 0:53 ` Alejandro Colomar
2023-11-13 22:27 ` Paul Eggert
2023-11-13 23:25 ` Alejandro Colomar
2023-11-12 23:52 ` [PATCH 3/4] strncat.3 fixes Paul Eggert
2023-11-13 1:15 ` Alejandro Colomar
2023-11-13 16:23 ` Alejandro Colomar
2023-11-21 16:03 ` Alejandro Colomar
2023-11-12 23:52 ` [PATCH 4/4] stpncpy(3) fixes Paul Eggert
2023-11-13 1:29 ` Alejandro Colomar
2023-11-21 18:33 ` Alejandro Colomar
2023-11-21 21:18 ` Paul Eggert
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=20231112235218.80195-1-eggert@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=linux-man@vger.kernel.org \
/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).