aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@member.fsf.org>2015-12-23 21:38:00 +0100
committerMattias Andrée <maandree@member.fsf.org>2015-12-23 21:38:00 +0100
commit0ca52f4202108b8ef18175bfbf7d5d5b137a8f8b (patch)
tree2de6faf20d09f25faad9ac6785d6dc1ab2806c16
parentm readme (diff)
downloadsat-0ca52f4202108b8ef18175bfbf7d5d5b137a8f8b.tar.gz
sat-0ca52f4202108b8ef18175bfbf7d5d5b137a8f8b.tar.bz2
sat-0ca52f4202108b8ef18175bfbf7d5d5b137a8f8b.tar.xz
m
Signed-off-by: Mattias Andrée <maandree@member.fsf.org>
-rw-r--r--README3
1 files changed, 2 insertions, 1 deletions
diff --git a/README b/README
index 63f5a78..d8058eb 100644
--- a/README
+++ b/README
@@ -21,7 +21,8 @@ RATIONALE
sat does not do natural language time parsing, it is far too complex,
and locale dependent, for all programs to implemeent and should be
- done in a separate program. sat does however do some trivial parsing.
+ done in a separate program. Not even GNU date(1) gets this right.
+ sat does however do some trivial parsing.
sat does not sanitise the environment. You have env(1) for that.
Relaying on sat to sanitise the environment appropriately could prove