summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>1997-07-14 18:32:12 +0000
committerJim Meyering <jim@meyering.net>1997-07-14 18:32:12 +0000
commit8c6a8c7743bec31fb8adfc2d8b080cff874ba8d9 (patch)
tree3ad00a627d2e4448a014c1f954b379452931a693 /doc
parent197d78d42818de0ed83d5c84c2a2a95d94e5a638 (diff)
downloadcoreutils-8c6a8c7743bec31fb8adfc2d8b080cff874ba8d9.tar.xz
tweak again
Diffstat (limited to 'doc')
-rw-r--r--doc/sh-utils.texi11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/sh-utils.texi b/doc/sh-utils.texi
index 925f0473e..6675a7a59 100644
--- a/doc/sh-utils.texi
+++ b/doc/sh-utils.texi
@@ -2459,8 +2459,8 @@ To convert a date string to the number of seconds since the epoch
the @samp{%s} format. That can be useful in sorting and/or graphing
and/or comparing data by date. The following command outputs the
number of the seconds since the epoch for the time one second later
-than the epoch, but in the time zone two hours later, thus a total
-of two hours and one second after the epoch:
+than the epoch, but in time zone two hours later (the Azores), thus
+a total of two hours and one second after the epoch:
@example
date --date='1970-01-01 00:00:01 UTC +2 hours' +%s
@@ -2469,12 +2469,13 @@ date --date='1970-01-01 00:00:01 UTC +2 hours' +%s
Suppose you had @emph{not} specified time zone information in the example above.
Then, date would have used your computer's idea of the time zone when
-interpreting the string. Here's what you would get if you were six
-hours later than UTC on that day:
+interpreting the string. Here's what you would get if you were in
+Greenwich, England:
@example
+# local time zone used
date --date='1970-01-01 00:00:01' +%s
-21601
+1
@end example
@item