linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: [PATCH] man7/*: srcfix: Correct the misuse of two-fonts macros
Date: Sun, 23 Feb 2020 21:30:55 +0000	[thread overview]
Message-ID: <20200223213055.GA2159@rhi.hi.is> (raw)

  Changes are based on the latest (23th Februar 2020) revision of my
local git repository.

  Correct the misuse of a two-font macro, which function is to

1) use the first font for each odd numbered argument and the second
font for all others.

2) join the arguments without an intervening space.

  There is no change in the output.

Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
---
 man7/cgroups.7          | 18 +++++++++---------
 man7/mount_namespaces.7 |  2 +-
 man7/uts_namespaces.7   |  2 +-
 3 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/man7/cgroups.7 b/man7/cgroups.7
index 493b7a10b..5173bbea4 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -788,7 +788,7 @@ frozen 0
 .PP
 The following keys may appear in this file:
 .TP
-.IR populated
+.I populated
 The value of this key is either 1,
 if this cgroup or any of its descendants has member processes,
 or otherwise 0.
@@ -799,13 +799,13 @@ The value of this key is 1 if this cgroup is currently frozen,
 or 0 if it is not.
 .PP
 The
-.IR cgroup.events
+.I cgroup.events
 file can be monitored, in order to receive notification when the value of
 one of its keys changes.
 Such monitoring can be done using
 .BR inotify (7),
 which notifies changes as
-.BR IN_MODIFY
+.B IN_MODIFY
 events, or
 .BR poll (2),
 which notifies changes by returning the
@@ -813,20 +813,20 @@ which notifies changes by returning the
 and
 .B POLLERR
 bits in the
-.IR revents
+.I revents
 field.
 .\"
 .SS Cgroup v2 release notification
 Cgroups v2 provides a new mechanism for obtaining notification
 when a cgroup becomes empty.
 The cgroups v1
-.IR release_agent
+.I release_agent
 and
-.IR notify_on_release
+.I notify_on_release
 files are removed, and replaced by the
 .I populated
 key in the
-.IR cgroup.events
+.I cgroup.events
 file.
 This key either has the value 0,
 meaning that the cgroup (and its descendants)
@@ -836,12 +836,12 @@ contains member processes.
 .PP
 The cgroups v2 release-notification mechanism
 offers the following advantages over the cgroups v1
-.IR release_agent
+.I release_agent
 mechanism:
 .IP * 3
 It allows for cheaper notification,
 since a single process can monitor multiple
-.IR cgroup.events
+.I cgroup.events
 files (using the techniques described earlier).
 By contrast, the cgroups v1 mechanism requires the expense of creating
 a process for each notification.
diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7
index 832d52282..584b223cd 100644
--- a/man7/mount_namespaces.7
+++ b/man7/mount_namespaces.7
@@ -1101,7 +1101,7 @@ may desire to prevent propagation of mount events to other mount namespaces
 .BR unshare (1)).
 This can be done by changing the propagation type of
 mount points in the new namespace to either
-.BR MS_SLAVE
+.B MS_SLAVE
 or
 .BR MS_PRIVATE .
 using a call such as the following:
diff --git a/man7/uts_namespaces.7 b/man7/uts_namespaces.7
index 3b30b6b3f..4db8c51e2 100644
--- a/man7/uts_namespaces.7
+++ b/man7/uts_namespaces.7
@@ -48,7 +48,7 @@ When a process creates a new UTS namespace using
 or
 .BR unshare (2)
 with the
-.BR CLONE_NEWUTS
+.B CLONE_NEWUTS
 flag, the hostname and domain of the new UTS namespace are copied
 from the corresponding values in the caller's UTS namespace.
 .PP
-- 
2.25.0

                 reply	other threads:[~2020-02-23 21:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200223213055.GA2159@rhi.hi.is \
    --to=bjarniig@rhi.hi.is \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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;
as well as URLs for NNTP newsgroup(s).