From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH v1 0/1] Document strnul(3)
Date: Sat, 21 Feb 2026 16:09:52 +0100 [thread overview]
Message-ID: <aZnKso6qQk-SMymf@devuan> (raw)
In-Reply-To: <aZnJYmxVIpqvaFZQ@devuan>
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
On 2026-02-21T16:04:24+0100, Alejandro Colomar wrote:
> On 2026-02-21T16:02:49+0100, Alejandro Colomar wrote:
> > Hi!
> >
> > gnulib has added strnul(3). I hope libc implementation eventually pick
> > up this API. Let's document it in a manual page.
>
> Here's how the page looks like:
>
> $ MANWIDTH=72 diffman-git HEAD
> fatal: path 'man/man3/strnul.3' exists on disk, but not in 'HEAD^'
> --- HEAD^:man/man3/strnul.3
> +++ HEAD:man/man3/strnul.3
> @@ -0,0 +1,39 @@
> +strnul(3) Library Functions Manual strnul(3)
> +
> +NAME
> + strnul - string null‐terminator
> +
> +LIBRARY
> + gnulib - The GNU Portability Library
> +
> +SYNOPSIS
> + #include <string.h>
> +
> + char *streq(const char *s);
Oops; s/streq/strnul/. Fixed.
> +
> +DESCRIPTION
> + strnul() returns a pointer to the terminating null byte in the
> + string s.
> +
> +RETURN VALUE
> + s+strlen(s).
> +
> +ATTRIBUTES
> + For an explanation of the terms used in this section, see attrib‐
> + utes(7).
> + ┌──────────────────────────────────────┬───────────────┬─────────┐
> + │ Interface │ Attribute │ Value │
> + ├──────────────────────────────────────┼───────────────┼─────────┤
> + │ strnul() │ Thread safety │ MT‐Safe │
> + └──────────────────────────────────────┴───────────────┴─────────┘
> +
> +STANDARDS
> + GNU.
> +
> +HISTORY
> + gnulib 202607.
> +
> +SEE ALSO
> + strlen(3), strchr(3), string(3)
> +
> +Linux man‐pages (unreleased) (date) strnul(3)
>
> --
> <https://www.alejandro-colomar.es>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-21 15:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 15:02 [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:02 ` [PATCH v1 1/1] man/man3/strnul.3: New page Alejandro Colomar
2026-02-21 17:41 ` G. Branden Robinson
2026-02-21 19:56 ` Alejandro Colomar
2026-02-21 20:02 ` Simon Josefsson
2026-02-21 20:45 ` Alejandro Colomar
2026-02-21 20:05 ` G. Branden Robinson
2026-02-21 20:55 ` Alejandro Colomar
2026-02-22 1:48 ` Paul Eggert
2026-02-22 11:21 ` Alejandro Colomar
2026-02-22 13:46 ` Alejandro Colomar
2026-02-22 14:10 ` Bruno Haible
2026-02-22 14:19 ` Alejandro Colomar
2026-02-22 14:21 ` Alejandro Colomar
2026-02-21 15:04 ` [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:09 ` Alejandro Colomar [this message]
2026-02-21 20:53 ` [PATCH v2 " Alejandro Colomar
2026-02-21 20:53 ` [PATCH v2 1/1] man/man3/strnul.3: New page 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=aZnKso6qQk-SMymf@devuan \
--to=alx@kernel.org \
--cc=bug-gnulib@gnu.org \
--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