From: Alejandro Colomar <alx@kernel.org>
To: dg@treblig.org
Cc: linux-man@vger.kernel.org, "Dr. David Alan Gilbert" <dave@treblig.org>
Subject: Re: [PATCH] man/man5/gai.conf: Fix RFC reference
Date: Sun, 4 Jan 2026 23:07:10 +0100 [thread overview]
Message-ID: <aVrkdFXRaSJvzDx4@devuan> (raw)
In-Reply-To: <20260104214956.258199-1-dg@treblig.org>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
Hi David,
On Sun, Jan 04, 2026 at 09:49:56PM +0000, dg@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <dave@treblig.org>
>
> Most of the RFC references correctly reference 3484, but the entry
> in scopev4 points to 3438 instead. It references section 3.2,
> which 3438 doesn't have, but 3484 does have and talks about IPv4
> addresses so looks right.
>
> Signed-off-by: Dr. David Alan Gilbert <dave@treblig.org>
Thanks! I've applied the patch.
Have a lovely night!
Alex
> ---
> man/man5/gai.conf.5 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man/man5/gai.conf.5 b/man/man5/gai.conf.5
> index d80c23311..4aff0b0b9 100644
> --- a/man/man5/gai.conf.5
> +++ b/man/man5/gai.conf.5
> @@ -61,7 +61,7 @@ .SH DESCRIPTION
> .TP
> .BI scopev4\~ mask\~value
> Add another rule to the RFC\ 3484 scope table for IPv4 address.
> -By default, the scope IDs described in section 3.2 in RFC\ 3438 are used.
> +By default, the scope IDs described in section 3.2 in RFC\ 3484 are used.
> Changing these defaults should hardly ever be necessary.
> .SH FILES
> .I /etc/gai.conf
> --
> 2.52.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-04 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 21:49 [PATCH] man/man5/gai.conf: Fix RFC reference dg
2026-01-04 22:07 ` Alejandro Colomar [this message]
2026-01-04 22:53 ` Dr. David Alan Gilbert
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=aVrkdFXRaSJvzDx4@devuan \
--to=alx@kernel.org \
--cc=dave@treblig.org \
--cc=dg@treblig.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