public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	linux-man@vger.kernel.org,  bug-gnulib@gnu.org
Subject: Re: [PATCH v1 1/1] man/man3/strnul.3: New page
Date: Sat, 21 Feb 2026 21:02:49 +0100	[thread overview]
Message-ID: <87fr6t7tli.fsf@josefsson.org> (raw)
In-Reply-To: <aZoMp9gUNpU6rGo4@devuan> (Alejandro Colomar's message of "Sat, 21 Feb 2026 20:56:05 +0100")

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

Alejandro Colomar <alx@kernel.org> writes:

> Hi Branden,
>
> On 2026-02-21T11:41:42-0600, G. Branden Robinson wrote:
>> Hi Alex,
>> 
>> At 2026-02-21T16:02:52+0100, Alejandro Colomar wrote:
>> > +.SH RETURN VALUE
>> > +.IR s+strlen(s) .
>> 
>> Too cute, in my opinion.  Use English.  :)
>
> The thing is, at first I thought, am I going to repeat the same exact
> words as in the DESCRIPTION?
>
> DESCRIPTION
>      strnul() returns a pointer to the terminating null byte in the
>      string s.
>
> RETURN VALUE
>      strnul() returns a pointer to the terminating null byte in the
>      string s.
>
> I could remove the DESCRIPTION altogether...  What would you do?

Use the same style as for strlen:

DESCRIPTION
       The  strlen() function calculates the length of the string pointed to by
       s, excluding the terminating null byte ('\0').

RETURN VALUE
       The strlen() function returns the number of bytes in the string  pointed
       to by s.

One says what it does, the other says what it returns.

/Simon

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1251 bytes --]

  reply	other threads:[~2026-02-21 20:23 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 [this message]
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
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=87fr6t7tli.fsf@josefsson.org \
    --to=simon@josefsson.org \
    --cc=alx@kernel.org \
    --cc=bug-gnulib@gnu.org \
    --cc=g.branden.robinson@gmail.com \
    --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