From eba53b965a87dfd5e86aab625cc24932dd057e58 Mon Sep 17 00:00:00 2001 From: "John W. De Boskey" Date: Fri, 28 Jul 2000 02:51:43 +0000 Subject: [PATCH] Try to clean the manpage up according to the mail from Sheldon in committers (Message-Id: <72836.964344168@axl.ops.uunet.co.za>). Also cleaned up a .Pq macro which was causing problems previous to the original update I made. Reviewed by: sheldonh Approved by: jkh --- bin/date/date.1 | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/bin/date/date.1 b/bin/date/date.1 index d9d7d705b95c..f47312290b0a 100644 --- a/bin/date/date.1 +++ b/bin/date/date.1 @@ -118,11 +118,10 @@ Print the date and time represented by where .Ar seconds is the number of seconds since the Epoch -.Po -00:00:00 UTC, January 1, 1970; +(00:00:00 UTC, January 1, 1970; see -.Xr time 3 -.Pc and can be specified in decimal, octal, or hex. +.Xr time 3 ) , +and can be specified in decimal, octal, or hex. .It Fl t Ar minutes_west Set the system's value for minutes west of .Tn GMT . @@ -195,7 +194,9 @@ the clock goes back at 02:00 to 01:00, using will be necessary to reach October 29, 2:30. .Pp When the date is adjusted to a specific value that doesn't actually exist -.Pq for example March 26, 1:30 BST 2000 in the Europe/London timezone , +.Po +for example March 26, 1:30 BST 2000 in the Europe/London timezone +.Pc , the date will be silently adjusted forwards in units of one hour until it reaches a valid time. When the date is adjusted to a specific value that occurs twice