linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Cyril Hrubis <chrubis-AlSwsSmVLrQ@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] link.2: Fix typo.
Date: Wed, 05 Mar 2014 12:14:53 +0100	[thread overview]
Message-ID: <5317072D.6050607@gmail.com> (raw)
In-Reply-To: <20140304160237.GA8347-HSzIOc4LzcM@public.gmane.org>

On 03/04/2014 05:02 PM, Cyril Hrubis wrote:
> protected_hardlink -> protected_hardlinks

Thanks, Cyrill.

Applied.

Cheers,

Michael

> 
> Signed-off-by: Cyril Hrubis <chrubis-AlSwsSmVLrQ@public.gmane.org>
> ---
>  man2/link.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/link.2 b/man2/link.2
> index 20c0b01..0311096 100644
> --- a/man2/link.2
> +++ b/man2/link.2
> @@ -245,7 +245,7 @@ does not support the creation of hard links.
>  .BR EPERM " (since Linux 3.6)"
>  The caller does not have permission to create a hard link to this file
>  (see the description of
> -.IR /proc/sys/fs/protected_hardlink
> +.IR /proc/sys/fs/protected_hardlinks
>  in
>  .BR proc (5)).
>  .TP
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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

      parent reply	other threads:[~2014-03-05 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 16:02 [PATCH] link.2: Fix typo Cyril Hrubis
     [not found] ` <20140304160237.GA8347-HSzIOc4LzcM@public.gmane.org>
2014-03-05 11:14   ` Michael Kerrisk (man-pages) [this message]

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=5317072D.6050607@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=chrubis-AlSwsSmVLrQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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).