All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fcntl.2: pfix
Date: Mon, 15 Sep 2014 11:10:48 +0200	[thread overview]
Message-ID: <5416AD18.30003@gmail.com> (raw)
In-Reply-To: <1410747921-16888-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>

Thanks, David. Applied.

Cheers,

Michael


On 09/15/2014 04:25 AM, David Prévot wrote:
> ---
>  man2/fcntl.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/fcntl.2 b/man2/fcntl.2
> index 77892a2..59f22ce 100644
> --- a/man2/fcntl.2
> +++ b/man2/fcntl.2
> @@ -475,7 +475,7 @@ in most respects identical to the traditional record locks described above.
>  This lock type is Linux-specific,
>  and available since Linux 3.15.
>  For an explanation of open file descriptions, see
> -.BR open (2)
> +.BR open (2).
>  
>  The principal difference between the two lock types
>  is that whereas traditional record locks
> 


-- 
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-09-15  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15  2:25 [PATCH] fcntl.2: pfix David Prévot
     [not found] ` <1410747921-16888-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-09-15  9:10   ` 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=5416AD18.30003@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=taffit-8fiUuRrzOP0dnm+yROfE0A@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.