public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: technoboy85@gmail.com
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Matteo Croce <teknoraver@meta.com>
Subject: [PATCH] proc.5: make literals bold
Date: Mon, 20 May 2024 12:59:56 +0200	[thread overview]
Message-ID: <20240520105956.71532-1-technoboy85@gmail.com> (raw)

From: Matteo Croce <teknoraver@meta.com>

Format the equal signs in the procfs mount options in bold to make it
clear that they are literal values.

Signed-off-by: Matteo Croce <teknoraver@meta.com>
---
 man/man5/proc.5 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man/man5/proc.5 b/man/man5/proc.5
index 5ae8fbf0c..d3bc28ff0 100644
--- a/man/man5/proc.5
+++ b/man/man5/proc.5
@@ -33,7 +33,7 @@ The
 .B proc
 filesystem supports the following mount options:
 .TP
-.BR hidepid "=\fIn\fP (since Linux 3.3)"
+.BR hidepid= "\fIn\fP (since Linux 3.3)"
 .\" commit 0499680a42141d86417a8fbaa8c8db806bea1201
 This option controls who can access the information in
 .IR /proc/ pid
@@ -91,7 +91,7 @@ some daemon is running with elevated privileges,
 whether another user is running some sensitive program,
 whether other users are running any program at all, and so on).
 .TP
-.BR gid "=\fIgid\fP (since Linux 3.3)"
+.BR gid= "\fIgid\fP (since Linux 3.3)"
 .\" commit 0499680a42141d86417a8fbaa8c8db806bea1201
 Specifies the ID of a group whose members are authorized to
 learn process information otherwise prohibited by
@@ -106,7 +106,7 @@ nonroot users into the
 file.
 .RE
 .TP
-.BR subset = pid " (since Linux 5.8)"
+.BR subset=pid " (since Linux 5.8)"
 .\" commit 6814ef2d992af09451bbeda4770daa204461329e
 Show only the specified subset of procfs,
 hiding all top level files and directories in the procfs
-- 
2.43.0


             reply	other threads:[~2024-05-20 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 10:59 technoboy85 [this message]
2024-05-26 10:11 ` [PATCH] proc.5: make literals bold 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=20240520105956.71532-1-technoboy85@gmail.com \
    --to=technoboy85@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=teknoraver@meta.com \
    /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