public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v4 02/10] ldconfig.8: Revise and update for glibc 2.32
Date: Sat, 7 Jan 2023 10:53:24 -0600	[thread overview]
Message-ID: <20230107165324.c2t2senoh3loyof4@illithid> (raw)
In-Reply-To: <43a8427b-4038-054e-cea1-c54417bf65bb@gmail.com>

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

Hi Alex,

At 2023-01-07T14:10:12+0100, Alejandro Colomar wrote:
> > * Expand description of "ld.so.conf" file to discuss "include" and
> >   "hwcap" features.  Describe these as "directives" (though the
> >   latter died upstream in glibc 2.32 before we got around to
> >   documenting it).  Document ld.so.conf's comment syntax.
> 
> I think ld.so.conf(4) might be a good manual page on its own, and
> ldconfig(1) refer to it.

s/1/8;s/4/5

That seems reasonable.  Can I tackle that _after_ the current batch is
off my plate?  :-O

> And maybe also for ld.so.cache(4).

(assuming s/4/5)

Here I don't agree.  The format of the cache file is an internal
implementation detail; the user can select a format (possibly for
file-sharing purposes[1]), but beyond the name of each format ("old",
"compat", "new"), these are opaque.

In my opinion a file format need be documented in section 5 only if it
is (deliberately) exposed to manipulation by other tools.

Regards,
Branden

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

  reply	other threads:[~2023-01-07 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07  9:54 [PATCH v4 02/10] ldconfig.8: Revise and update for glibc 2.32 G. Branden Robinson
2023-01-07 13:10 ` Alejandro Colomar
2023-01-07 16:53   ` G. Branden Robinson [this message]
2023-01-07 19:39     ` Alejandro Colomar
2023-01-08 23:00       ` G. Branden Robinson

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=20230107165324.c2t2senoh3loyof4@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@gmail.com \
    --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