From: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: [PATCH] proc.5: ffix
Date: Thu, 10 May 2012 11:57:28 -0400 [thread overview]
Message-ID: <1336665448-7303-1-git-send-email-taffit@debian.org> (raw)
---
man5/proc.5 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man5/proc.5 b/man5/proc.5
index ace0941..2ba1daa 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -95,7 +95,7 @@ The format is one \fIunsigned long\fP ID
plus one \fIunsigned long\fP value for each entry.
The last entry contains two zeros.
.TP
-.I /proc/[pid]/cgroup " (since Linux 2.6.24)"
+.IR /proc/[pid]/cgroup " (since Linux 2.6.24)"
.\" Info in Documentation/cgroups/cgroups.txt
This file describes control groups to which the process/task belongs.
For each cgroup hierarchy there is one entry containing
--
1.7.10
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-05-10 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 15:57 David Prévot [this message]
[not found] ` <1336665448-7303-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-10 18:25 ` [PATCH] proc.5: ffix Michael Kerrisk (man-pages)
2013-03-25 22:58 Simon Paillard
[not found] ` <1364252338-14762-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-03-28 9:15 ` Michael Kerrisk (man-pages)
2014-08-02 21:13 Simon Paillard
[not found] ` <1407013980-31378-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-08-03 10:23 ` Michael Kerrisk (man-pages)
2020-05-30 15:58 Jakub Wilk
2020-06-08 15:41 ` Michael Kerrisk (man-pages)
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=1336665448-7303-1-git-send-email-taffit@debian.org \
--to=taffit-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).