From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] manual: Fix some @code/@var formatting glitches chapter Date And Time
Date: Wed, 05 Aug 2020 09:23:14 +0200 [thread overview]
Message-ID: <87o8npy2sd.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <87h7wdcrr7.fsf@oldenburg2.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 18 May 2020 15:11:24 +0200")
* Florian Weimer via Libc-alpha:
> ---
> Changes in v2: Rebased to current master.
>
> manual/time.texi | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/manual/time.texi b/manual/time.texi
> index 164c150f64..0c7a942b4c 100644
> --- a/manual/time.texi
> +++ b/manual/time.texi
> @@ -803,11 +803,11 @@ exceeded the threshold.
> The @code{ntp_adjtime} function sets the structure specified by
> @var{tptr} to current values.
>
> -In addition, @code{ntp_adjtime} updates some settings to match what you
> -pass to it in *@var{tptr}. Use the @code{modes} element of *@var{tptr}
> -to select what settings to update. You can set @code{offset},
> -@code{freq}, @code{maxerror}, @code{esterror}, @code{status},
> -@code{constant}, and @code{tick}.
> +In addition, @code{ntp_adjtime} updates some settings to match what
> +you pass to it in @code{*@var{tptr}}. Use the @code{modes} element of
> +@code{*@var{tptr}} to select what settings to update. You can set
> +@code{offset}, @code{freq}, @code{maxerror}, @code{esterror},
> +@code{status}, @code{constant}, and @code{tick}.
>
> @code{modes} = zero means set nothing.
>
> @@ -3018,12 +3018,12 @@ nanoseconds. The actual elapsed time of the sleep interval might be
> longer since the system rounds the elapsed time you request up to the
> next integer multiple of the actual resolution the system can deliver.
>
> -*@code{requested_time} is the elapsed time of the interval you want to
> -sleep.
> +@code{*@var{requested_time}} is the elapsed time of the interval you
> +want to sleep.
>
> -The function returns as *@code{remaining} the elapsed time left in the
> -interval for which you requested to sleep. If the interval completed
> -without getting interrupted by a signal, this is zero.
> +The function returns as @code{*@var{remaining}} the elapsed time left
> +in the interval for which you requested to sleep. If the interval
> +completed without getting interrupted by a signal, this is zero.
>
> @code{struct timespec} is described in @ref{Time Types}.
>
Ping? This patch still needs review.
Thanks,
Florian
next prev parent reply other threads:[~2020-08-05 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 13:11 [PATCH v2] manual: Fix some @code/@var formatting glitches chapter Date And Time Florian Weimer via Libc-alpha
2020-08-05 7:23 ` Florian Weimer via Libc-alpha [this message]
2020-08-05 14:29 ` Paul Eggert
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8npy2sd.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).