Linux Manual Pages development
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 2/4] man/man5/tunables.conf: Document system-wide tunables config
Date: Mon, 03 Aug 2026 15:26:23 -0400	[thread overview]
Message-ID: <xn33wv57kw.fsf@greed.delorie.com> (raw)
In-Reply-To: <am1GD8EYQqLBrXCT@devuan> (message from Alejandro Colomar on Sat, 1 Aug 2026 03:13:01 +0200)

Alejandro Colomar <alx@kernel.org> writes:
> '-' should be escaped: '\-'

Fixed.

> Also, these examples don't need bold.  We use bold to differentiate from
> program output, when we have examples that show both a command and its
> output.  In this case, being just a simple command, it's fine in roman.
>
> 	ld.so \-\-list\-tunables

Fixed.

> For consistency with patch 1/4, this should use the same wording:
>
> 	The syntax allows lines to start with the keyword
> 	.B include
> 	followed by a
> 	.BR glob (7)
> 	pattern.
>
> It's also much simpler.

Fixed.  I thought I got all of those in sync...

>> +The file is parsed by
>> +.BR \%ldconfig (8)
>> +and the results stored in
>> +.IR /etc/ld.so.cache .
>
> In patch 1/4 (ld.so.conf(5)), this paragraph is specified above the
> specification of 'include'.  We should be consistent.  Do you prefer it
> above in both, or below in both?

I moved it here.

> (I haven't pushed patch 1 yet, so if you want to modify it, I can amend
>  it.)

Well, you did push it ;-)

I added a signed-off-by to the new 2/4 but I've never had to do that due
to Red Hat's blanket copyright assignments everywhere.  Assuming those
are in place for man-pages, I was under the impression that a
signed-off-by would be contra-indicated.


  reply	other threads:[~2026-08-03 20:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 18:22 [PATCH v3 0/4] Tunables-related updates DJ Delorie
2026-07-31 18:22 ` [PATCH v3 1/4] man/man5/ld.so.conf.5: document include syntax DJ Delorie
2026-07-31 18:22   ` [PATCH v3 2/4] man/man5/tunables.conf: Document system-wide tunables config DJ Delorie
2026-07-31 18:22     ` [PATCH v3 3/4] man/man8/ld.so.8: Note that ld.so.cache includes tunables DJ Delorie
2026-07-31 18:22       ` [PATCH v3 4/4] man/man8/ldconfig.8: Add tunables options DJ Delorie
2026-08-01  1:16         ` Alejandro Colomar
2026-08-01  1:14       ` [PATCH v3 3/4] man/man8/ld.so.8: Note that ld.so.cache includes tunables Alejandro Colomar
2026-08-01  1:13     ` [PATCH v3 2/4] man/man5/tunables.conf: Document system-wide tunables config Alejandro Colomar
2026-08-03 19:26       ` DJ Delorie [this message]
2026-08-03 23:19         ` Alejandro Colomar
2026-08-01  1:01   ` [PATCH v3 1/4] man/man5/ld.so.conf.5: document include syntax 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=xn33wv57kw.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=alx@kernel.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