public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Dr. David Alan Gilbert" <dave@treblig.org>
Cc: linux-man@vger.kernel.org
Subject: Re: gai.conf(5): Example table
Date: Mon, 5 Jan 2026 14:19:01 +0100	[thread overview]
Message-ID: <aVu5_QZHJAjYFKA7@devuan> (raw)
In-Reply-To: <aVr_-WDqRyRBL_G_@gallifrey>

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

Hi Dave,

On Mon, Jan 05, 2026 at 12:04:09AM +0000, Dr. David Alan Gilbert wrote:
> Hi,
>   The 'EXAMPLES' section in gai.conf(5) has a table that matches
> RFC 3484; however that's not what glibc's default label table is;
> it's table has three extra entries:
> 
> https://sourceware.org/git/?p=glibc.git;a=blob;f=nss/getaddrinfo.c;h=c0f496f96c752220e68bf0257d9ff1ffc624ebe6;hb=HEAD#l1341
> 
> and partially in the more readable:
> https://sourceware.org/git/?p=glibc.git;a=blob;f=posix/gai.conf;h=4616ed005b2e064175c88609b6d6022a6da4d5d8;hb=HEAD#l31
> 
> I wonder if it makes sense to document glibc's default rather than the
> RFC default?

Yup; feel free to send patches documenting the glibc behavior.  It would
also be good to note that those differences are specific to glibc.


Have a lovely New Year!
Alex

> 
> Dave
> -- 
>  -----Open up your eyes, open up your mind, open up your code -------   
> / Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
> \        dave @ treblig.org |                               | In Hex /
>  \ _________________________|_____ http://www.treblig.org   |_______/

-- 
<https://www.alejandro-colomar.es>

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

      reply	other threads:[~2026-01-05 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05  0:04 gai.conf(5): Example table Dr. David Alan Gilbert
2026-01-05 13:19 ` Alejandro Colomar [this message]

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=aVu5_QZHJAjYFKA7@devuan \
    --to=alx@kernel.org \
    --cc=dave@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