public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Melker Narikka <meklu@meklu.org>, linux-man@vger.kernel.org
Cc: Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] clock_nanosleep.2: tfix CLOCK_BOOTTIME
Date: Mon, 25 Oct 2021 22:34:33 +0200	[thread overview]
Message-ID: <ce45ad62-9403-99fc-a767-252fecb3ec48@gmail.com> (raw)
In-Reply-To: <CAFbsDtgjmDEHXfy2xB4zt4MM5uZtOWZcT42B1QoFGC-DJgHQNg@mail.gmail.com>

Hello Melker,

On 10/25/21 8:28 PM, Melker Narikka wrote:
> From: Melker Narikka <meklu@meklu.org>
> 
> Signed-off-by: Melker Narikka <meklu@meklu.org>

Patch applied! Thanks.

BTW, check your mailer; it broke the patch by introducing a line break.

Cheers,

Alex

> ---
>   man2/clock_nanosleep.2 | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/clock_nanosleep.2 b/man2/clock_nanosleep.2
> index b8c4afc2c..1d607e1ce 100644
> --- a/man2/clock_nanosleep.2
> +++ b/man2/clock_nanosleep.2
> @@ -90,7 +90,7 @@ since some unspecified point in the past that does
> not change after

The above lines are 2 separate lines, instead of a single line.
I fixed that manually.

>   system startup.
>   .\" On Linux this clock measures time since boot.
>   .TP
> -.BR CLOCK_BOOTIME " (since Linux 2.6.39)"
> +.BR CLOCK_BOOTTIME " (since Linux 2.6.39)"
>   Identical to
>   .BR CLOCK_MONOTONIC ,
>   except that it also includes any time that the system is suspended.
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2021-10-25 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 18:28 [PATCH] clock_nanosleep.2: tfix CLOCK_BOOTTIME Melker Narikka
2021-10-25 20:34 ` Alejandro Colomar (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=ce45ad62-9403-99fc-a767-252fecb3ec48@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=meklu@meklu.org \
    --cc=mtk.manpages@gmail.com \
    /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