From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] utmp.5: Oxford comma
Date: Sat, 21 Nov 2020 22:27:02 +0100 [thread overview]
Message-ID: <512e1381-1ef0-3628-c256-60d06a478f6f@gmail.com> (raw)
In-Reply-To: <20201121173903.12429-1-alx.manpages@gmail.com>
On 11/21/20 6:39 PM, Alejandro Colomar wrote:
> Found using:
> $ grep -rn '\\f., [^ ]*\\f. and' man?
>
> I also updated the markup in that paragraph: \f -> .
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks, ALex.
Patch applied.
Cheers,
Michael
> ---
> man5/utmp.5 | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/man5/utmp.5 b/man5/utmp.5
> index 3b8340858..3b8afc199 100644
> --- a/man5/utmp.5
> +++ b/man5/utmp.5
> @@ -176,9 +176,18 @@ records may be located by
> .PP
> When
> .BR init (1)
> -finds that a process has exited, it locates its utmp
> -entry by \fIut_pid\fP, sets \fIut_type\fP to \fBDEAD_PROCESS\fP, and
> -clears \fIut_user\fP, \fIut_host\fP and \fIut_time\fP with null bytes.
> +finds that a process has exited, it locates its utmp entry by
> +.IR ut_pid ,
> +sets
> +.I ut_type
> +to
> +.BR DEAD_PROCESS ,
> +and clears
> +.IR ut_user ,
> +.IR ut_host ,
> +and
> +.I ut_time
> +with null bytes.
> .PP
> .BR xterm (1)
> and other terminal emulators directly create a
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-11-21 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 17:39 [PATCH] utmp.5: Oxford comma Alejandro Colomar
2020-11-21 21:27 ` 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=512e1381-1ef0-3628-c256-60d06a478f6f@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.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).