From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] manual: Fix some @code/@var formatting glitches chapter Date And Time
Date: Mon, 09 Sep 2019 11:39:28 +0200 [thread overview]
Message-ID: <87zhjdlsfj.fsf@oldenburg2.str.redhat.com> (raw)
2019-09-09 Florian Weimer <fweimer@redhat.com>
* manual/time.texi (High Accuracy Clock): Fix @code/@var formatting.
(Sleeping): Likewise.
diff --git a/manual/time.texi b/manual/time.texi
index c5f5b94b67..46d0f9d482 100644
--- a/manual/time.texi
+++ b/manual/time.texi
@@ -1103,11 +1103,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.
@@ -2878,12 +2878,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 @xref{Elapsed Time}.
reply other threads:[~2019-09-09 9:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zhjdlsfj.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).