From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: maxin.john-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Maxin B. John" <maxin.john-AM1FMPraTHU@public.gmane.org>
Subject: Re: [PATCH] flock.2: update documentation path
Date: Sat, 26 Oct 2013 11:05:23 +1300 [thread overview]
Message-ID: <526AEB23.1000109@gmail.com> (raw)
In-Reply-To: <1381265274-5450-1-git-send-email-maxin.john-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 09.10.2013 09:47, maxin.john-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> From: "Maxin B. John" <maxin.john-AM1FMPraTHU@public.gmane.org>
>
> Update the Kernel Documentation path for flock
>
> Signed-off-by: Maxin B. John <maxin.john-AM1FMPraTHU@public.gmane.org>
> ---
> man2/flock.2 | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/man2/flock.2 b/man2/flock.2
> index ee3e1c1..838cc7e 100644
> --- a/man2/flock.2
> +++ b/man2/flock.2
> @@ -208,7 +208,7 @@ and occurs on many other implementations.)
> .BR open (2),
> .BR lockf (3)
>
> -.I Documentation/filesystem/locks.txt
> +.I Documentation/filesystems/locks.txt
> in the Linux kernel source tree
> .RI ( Documentation/locks.txt
> in older kernels)
Applied.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
My next Linux/UNIX system programming course:
--
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
prev parent reply other threads:[~2013-10-25 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 20:47 [PATCH] flock.2: update documentation path maxin.john-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1381265274-5450-1-git-send-email-maxin.john-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-25 22:05 ` 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=526AEB23.1000109@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maxin.john-AM1FMPraTHU@public.gmane.org \
--cc=maxin.john-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.