From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [PATCH] getline.3: wfix.
Date: Fri, 29 Jul 2022 15:52:38 -0500 [thread overview]
Message-ID: <20220729205238.6yf4c4xc2i5ritp3@illithid> (raw)
In-Reply-To: <CAJgzZopm7h_0_4j=grKiOu5tWr87ik4-nNvMRy1gxxH_b5b7dQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
Hi Elliott,
At 2022-07-29T13:22:22-0700, enh wrote:
> Clarify in the RETURN VALUE section that it's necessary to free the
> buffer, since at least one person missed this up at the start of the
> DESCRIPTION.
[...]
> +If
> +.I "*lineptr"
The quotation marks are unnecessary; macro arguments are space-delimited
and you have none here. (Even if you had multiple arguments, macros
like `B` and `I` treat them all the same.)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-29 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 20:22 [PATCH] getline.3: wfix enh
2022-07-29 20:52 ` G. Branden Robinson [this message]
2022-07-29 20:55 ` enh
2022-08-01 12:53 ` Alejandro Colomar
2022-08-02 21:17 ` enh
2022-08-05 19:20 ` italicizing pointer stars (was: [PATCH] getline.3: wfix.) G. Branden Robinson
2022-08-05 19:40 ` Alejandro Colomar
2022-08-05 21:49 ` G. Branden Robinson
2022-08-05 21:56 ` Alejandro Colomar
2022-08-15 21:16 ` [PATCH] getline.3: wfix Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2017-07-12 8:10 Long Wang
[not found] ` <1499847001-83794-1-git-send-email-w-m92B/FuLcaEcWVvVuXF20w@public.gmane.org>
2017-07-12 17:36 ` 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=20220729205238.6yf4c4xc2i5ritp3@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=enh@google.com \
--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