From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page getent.1
Date: Wed, 1 Nov 2023 16:38:35 +0100 [thread overview]
Message-ID: <ZUJw-w5mCUQIL63N@debian> (raw)
In-Reply-To: <ZUJaYgd8DCnFdm1V@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Wed, Nov 01, 2023 at 02:02:10PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: B<hosts> → B<hosts>(5)
Thanks! Fixed:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=f0d0efdf3e3997b00edaca6f7aa0c6a9b5e8d1cc>
Cheers,
Alex
>
> "When no I<key> is provided, use B<sethostent>(3), B<gethostent>(3), and "
> "B<endhostent>(3) to enumerate the hosts database. This is identical to "
> "using B<hosts>. When one or more I<key> arguments are provided, pass each "
> "I<key> in succession to B<getaddrinfo>(3) with the address family "
> "B<AF_UNSPEC>, enumerating each socket address structure returned."
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Issue in man page getent.1 Helge Kreutzmann
2023-11-01 15:38 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 15:30 ` Alejandro Colomar
2023-11-01 15:44 ` Helge Kreutzmann
2023-11-11 19:49 ` Alejandro Colomar
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 15:28 ` Alejandro Colomar
2024-11-19 13:14 ` Carlos O'Donell
2024-11-19 13:19 ` 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=ZUJw-w5mCUQIL63N@debian \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@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