From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Simon Paillard
<spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] ffix: add space between function and () if BR or IR
Date: Mon, 10 Feb 2014 11:04:30 +0100 [thread overview]
Message-ID: <52F8A42E.1060708@gmail.com> (raw)
In-Reply-To: <1391861950-6509-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Thanks, Simon. Applied.
I'll put together a script to make these and other checks.
Cheers,
Michael
On 02/08/2014 01:19 PM, Simon Paillard wrote:
> Detected through the regex:
> git grep -P '^\.(BR|IR) [\w]*\([\d]*\)$'
> ---
> man3/getgrent.3 | 6 +++---
> man3/getpwent.3 | 6 +++---
> man7/socket.7 | 4 ++--
> 3 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/man3/getgrent.3 b/man3/getgrent.3
> index d666bd3..b357cda 100644
> --- a/man3/getgrent.3
> +++ b/man3/getgrent.3
> @@ -155,13 +155,13 @@ local group database file
> .SH ATTRIBUTES
> .SS Multithreading (see pthreads(7))
> The
> -.BR getgrent()
> +.BR getgrent ()
> function is not thread-safe.
> .LP
> The
> -.BR setgrent()
> +.BR setgrent ()
> and
> -.BR endgrent()
> +.BR endgrent ()
> functions are thread-safe.
> .SH CONFORMING TO
> SVr4, 4.3BSD, POSIX.1-2001.
> diff --git a/man3/getpwent.3 b/man3/getpwent.3
> index de31c60..fb78171 100644
> --- a/man3/getpwent.3
> +++ b/man3/getpwent.3
> @@ -154,13 +154,13 @@ local password database file
> .SH ATTRIBUTES
> .SS Multithreading (see pthreads(7))
> The
> -.BR getpwent()
> +.BR getpwent ()
> function is not thread-safe.
> .LP
> The
> -.BR setpwent()
> +.BR setpwent ()
> and
> -.BR endpwent()
> +.BR endpwent ()
> functions are thread-safe.
> .SH CONFORMING TO
> SVr4, 4.3BSD, POSIX.1-2001.
> diff --git a/man7/socket.7 b/man7/socket.7
> index 9421686..9e2c23d 100644
> --- a/man7/socket.7
> +++ b/man7/socket.7
> @@ -452,7 +452,7 @@ For more information see
> This option, which is currently supported only for
> .BR unix (7)
> sockets, sets the value of the "peek offset" for the
> -.BR recv(2)
> +.BR recv (2)
> system call when used with
> .BR MSG_PEEK
> flag.
> @@ -460,7 +460,7 @@ flag.
> When this option is set to a negative value
> (it is set to \-1 for all new sockets),
> traditional behavior is provided:
> -.BR recv(2)
> +.BR recv (2)
> with the
> .BR MSG_PEEK
> flag will peek data from the front of the queue.
>
--
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
prev parent reply other threads:[~2014-02-10 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 12:19 [PATCH] ffix: add space between function and () if BR or IR Simon Paillard
[not found] ` <1391861950-6509-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-02-10 10:04 ` 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=52F8A42E.1060708@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spaillard-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.