From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Benjamin Peterson <benjamin@python.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] clock_getres.2: tfix
Date: Sun, 29 Mar 2020 09:21:23 +0200 [thread overview]
Message-ID: <16430107-a6a7-7a2d-c9e7-cc0a64a9b3fb@gmail.com> (raw)
In-Reply-To: <20200327041749.21337-1-benjamin@python.org>
On 3/27/20 5:17 AM, Benjamin Peterson wrote:
> Signed-off-by: Benjamin Peterson <benjamin@python.org>
Thanks, Benjamin. Applied.
Cheers,
Michael
> ---
> man2/clock_getres.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
> index d8b02e185..4422d2d00 100644
> --- a/man2/clock_getres.2
> +++ b/man2/clock_getres.2
> @@ -139,7 +139,7 @@ and probably also architecture support for this flag in the
> .TP
> .BR CLOCK_TAI " (since Linux 3.10; Linux-specific)"
> .\" commit 1ff3c9677bff7e468e0c487d0ffefe4e901d33f4
> -A system-wide clock derived from walli-clock time but ignoring leap seconds.
> +A system-wide clock derived from wall-clock time but ignoring leap seconds.
> This clock does
> not experience discontinuities and backwards jumps caused by NTP
> inserting leap seconds as
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-03-29 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 4:17 [PATCH] clock_getres.2: tfix Benjamin Peterson
2020-03-29 7:21 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 18:53 Jakub Wilk
2023-03-31 19:50 ` Alejandro Colomar
2012-05-07 19:34 David Prévot
[not found] ` <1336419296-4823-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-07 21:20 ` Michael Kerrisk (man-pages)
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=16430107-a6a7-7a2d-c9e7-cc0a64a9b3fb@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=benjamin@python.org \
--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).