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: tfix
Date: Sat, 20 Oct 2012 15:44:58 -0400 [thread overview]
Message-ID: <1350762298-6184-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 5337160..5312314 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -2036,7 +2036,7 @@ The minimum value that can be assigned to this file is the system page size.
.IR /proc/sys/fs/protected_hardlinks " (since Linux 3.6)"
.\" commit 800179c9b8a1e796e441674776d11cd4c05d61d7
When the value in this file is 0,
-no restrictions are placed the creation of hard links
+no restrictions are placed on the creation of hard links
(i.e., this is the historical behaviour before Linux 3.6).
When the value in this file is 1,
a hard link can be created to a target file
--
1.7.10.4
--
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-10-20 19:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 19:44 David Prévot [this message]
[not found] ` <1350762298-6184-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-10-21 6:41 ` [PATCH] proc.5: tfix Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2012-11-03 22:53 Simon Paillard
[not found] ` <1351983187-7963-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-11-05 16:17 ` Michael Kerrisk (man-pages)
2012-12-23 13:16 David Prévot
[not found] ` <1356268602-15896-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-12-23 17:52 ` Michael Kerrisk (man-pages)
2013-03-29 21:55 David Prévot
[not found] ` <1364594142-24998-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-04-01 6:25 ` Michael Kerrisk (man-pages)
2014-02-01 18:22 David Prévot
[not found] ` <1391278965-26411-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-02-04 9:02 ` Michael Kerrisk (man-pages)
2015-05-13 9:50 Marko Myllynen
[not found] ` <55531E73.2020405-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-13 12:05 ` Michael Kerrisk (man-pages)
2016-08-07 10:47 Jakub Wilk
[not found] ` <1470566838-8148-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-08-07 17:47 ` Michael Kerrisk (man-pages)
2017-10-08 15:53 Jakub Wilk
[not found] ` <20171008155334.6909-1-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2017-10-08 18:50 ` Michael Kerrisk (man-pages)
2020-03-11 22:56 Jakub Wilk
2020-03-12 5:41 ` Michael Kerrisk (man-pages)
2020-07-20 5:59 Jakub Wilk
2020-07-20 9:27 ` Michael Kerrisk (man-pages)
2022-10-06 13:06 [patch] " Andrea Cervesato
2022-10-08 1:52 ` 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=1350762298-6184-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).