Skip to content

Commit 5b493e4

Browse files
committed
Fix reference to epoch in the tutorial
1 parent 0b293fc commit 5b493e4

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/tutorial_basic.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -431,10 +431,10 @@ Date Handling
431431
-------------
432432

433433
The other important switches are those used in the detection of dates encoded
434-
as numbers: :option:`structa --min-timestamp` and :option:`structa
435-
--max-timestamp`. When dates are encoded as (potentially fractional)
436-
day-offsets from some :option:`structa --epoch` (which defaults to the UNIX
437-
epoch, i.e. the 1st January, 1970), how does structa determine that it's
434+
as numbers: :option:`structa --min-timestamp`, :option:`structa
435+
--max-timestamp`, and :option:`structa --timestamps`. When dates are encoded as
436+
(potentially fractional) day-offsets from some epoch (which defaults to the
437+
UNIX epoch, i.e. the 1st January, 1970), how does structa determine that it's
438438
looking at a set of dates rather than a set of numbers?
439439

440440
In a typical set of (arbitrary) numbers, it's quite normal to find "0" or "1"

0 commit comments

Comments
 (0)