From 45d8382fb2cc3f32b176675c0edb7eef5ca6aa21 Mon Sep 17 00:00:00 2001
From: Russ Allbery <rra@stanford.edu>
Date: Sat, 1 Dec 2007 01:55:18 +0000
Subject: Expiration dates are now expressed in YYYY-MM-DD HH:MM:SS instead of
 seconds since epoch and returned the same way.  Timestamps are now stored in
 the database as correct date and time types rather than seconds since epoch
 to work properly with MySQL.

---
 client/wallet.pod | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'client')

diff --git a/client/wallet.pod b/client/wallet.pod
index 779e691..af7042d 100644
--- a/client/wallet.pod
+++ b/client/wallet.pod
@@ -195,10 +195,10 @@ If <expires> is not given, displays the current expiration of the object
 identified by <type> and <name>, or C<No expiration set> if none is set.
 The expiration will be displayed in seconds since epoch.
 
-If <expires> is given, sets the expiration on the object identified by
-<type> and <name> to <expires>.  <expires> should be given in seconds
-since epoch.  If <expires> is the empty string, clears the expiration of
-the object.
+If <date> is given, sets the expiration on the object identified by <type>
+and <name> to <date> and (if given) <time>.  <date> must be in the format
+C<YYYY-MM-DD> and <time> in the format C<HH:MM:SS>.  If <date> is the empty
+string, clears the expiration of the object.
 
 Currently, the expiration of an object is not used.
 
-- 
cgit v1.2.3