From: Alejandro Colomar <alx@kernel.org>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page bcmp.3.
Date: Thu, 2 Nov 2023 12:32:34 +0100 [thread overview]
Message-ID: <ZUOI0sqWLx07vFVW@debian> (raw)
In-Reply-To: <CACKs7VAKY4tvY3yEq3Y6x10MBaY+_jW37_VJWbpZX0dX5V+cEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Thu, Nov 02, 2023 at 12:06:34PM +0200, Stefan Puiu wrote:
> Hi Alex,
>
> On Wed, Nov 1, 2023 at 6:25 PM Alejandro Colomar <alx@kernel.org> wrote:
> >
> > Hi Helge,
> >
> > On Wed, Nov 01, 2023 at 02:02:12PM +0000, Helge Kreutzmann wrote:
> > > Without further ado, the following was found:
> > >
> > > Issue: Who is "it"?
> > > "B<bcmp>() is identical to B<memcmp>(3); use it instead."
> >
> > Considering that the rest of the page is there just to say this function
> > is deprecated and even removed from POSIX, I guess a suggestion to use
> > 'it' can only mean use the other one, that is, memcmp(3).
>
> Maybe 'use the latter instead' would be clearer?
I've applied that fix:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=b8584be144ff391354190f89c4db4467ba0f9e53>
Cheers,
Alex
>
> Thanks,
> Stefan.
>
>
> >
> >[..]
> > <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:[~2023-11-02 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Issue in man page bcmp.3 Helge Kreutzmann
2023-11-01 16:24 ` Alejandro Colomar
2023-11-02 10:06 ` Stefan Puiu
2023-11-02 11:27 ` Alejandro Colomar
2023-11-02 11:32 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
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=ZUOI0sqWLx07vFVW@debian \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
--cc=stefan.puiu@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