From: DJ Delorie <dj@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v4 2/4] man/man5/tunables.conf: Document system-wide tunables config
Date: Thu, 06 Aug 2026 16:17:36 -0400 [thread overview]
Message-ID: <xn5x1n3swv.fsf@greed.delorie.com> (raw)
In-Reply-To: <anTZdJDceYtD7Rfj@devuan> (message from Alejandro Colomar on Thu, 6 Aug 2026 21:14:28 +0200)
Alejandro Colomar <alx@kernel.org> writes:
> Hmmmm, let's see. I couldn't do it in five words, but how about this
> schematic approach?
>
> The file may also contain
> .IR filters ,
> which limit the tunables following it,
> The effects of a filter are terminated by
> any of the following:
> .IP \[bu] 3
> The end of the file.
> .IP \[bu]
> The end of an included file.
> .IP \[bu]
> An
> .B include
> directive.
> .IP \[bu]
> A new (possibly empty) filter.
I like it as-is, other than "why are there blank lines" but I don't care
about that ;-)
> Since a filter can be empty, we should document that. If we document
> that 'filter:pattern' is optional, it'd be [[filter:pattern]] (with the
> appropriate formatting differences: the inner '[' wouldn't be bold).
> However, that's likely to be confusing, so let's document that
> separately:
>
> A filter can also be empty:
> .BR [] .
> Such a filter has no effects.
Done. I put it after the filter list, so the "also" made sense.
next prev parent reply other threads:[~2026-08-06 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 19:21 [PATCH v4 2/4] man/man5/tunables.conf: Document system-wide tunables config DJ Delorie
2026-08-06 14:37 ` Alejandro Colomar
2026-08-06 15:33 ` DJ Delorie
2026-08-06 19:14 ` Alejandro Colomar
2026-08-06 20:17 ` DJ Delorie [this message]
2026-08-06 20:31 ` Alejandro Colomar
2026-08-06 20:42 ` DJ Delorie
2026-08-07 2:12 ` G. Branden Robinson
2026-08-07 3:29 ` DJ Delorie
2026-08-07 3:49 ` G. Branden Robinson
2026-08-07 4:01 ` DJ Delorie
2026-08-07 4:09 ` 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=xn5x1n3swv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.