All of lore.kernel.org
 help / color / mirror / Atom feed
From: J William Piggott <elseifthen@gmx.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH] hwclock: improve man-page language
Date: Mon, 16 Feb 2015 07:55:31 -0500	[thread overview]
Message-ID: <54E1E8C3.30704@gmx.com> (raw)

Signed-off-by: J William Piggott <elseifthen@gmx.com>
---
 sys-utils/hwclock.8.in | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/sys-utils/hwclock.8.in b/sys-utils/hwclock.8.in
index 7ddd2b1..b13be31 100644
--- a/sys-utils/hwclock.8.in
+++ b/sys-utils/hwclock.8.in
@@ -993,12 +993,13 @@ A discussion on date-time configuration would be incomplete without
 addressing timezones, this is mostly well covered by
 .BR tzset (3).
 One area that seems to have no documentation is the 'right'
-directory of the Time Zone Database, aka tz, aka zoneinfo.
+directory of the Time Zone Database, sometimes called tz or zoneinfo.
 .PP
 There are two separate databases in the zoneinfo system, posix
 and 'right'. 'Right' (now named zoneinfo\-leaps) includes leap seconds and posix
-does not. To use the 'right' database the System Clock must be kept in
-\%UTC\ +\ leap_seconds, i.e., \%TAI\ \-\ 10. This allows calculating the
+does not. To use the 'right' database the System Clock must be set to
+\%(UTC\ +\ leap seconds), which is equivalent to \%(TAI\ \-\ 10). This
+allows calculating the
 exact number of seconds between two dates that cross a leap second
 epoch. The System Clock is then converted to the correct civil time,
 including UTC, by using the 'right' timezone files which subtract the

             reply	other threads:[~2015-02-16 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 12:55 J William Piggott [this message]
2015-02-19  9:54 ` [PATCH] hwclock: improve man-page language Karel Zak

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=54E1E8C3.30704@gmx.com \
    --to=elseifthen@gmx.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.