At present, the only thing affected is 'log'. My immediate thought is
that absolutely we should *not* apply these changes to the automate
interface, because that's intended for machine consumption; in
particular, you don't want to have to parse whatever arbitrary gunk
the user put in their date format spec.
On the other hand I've never written anything that consumed automate
output. Are there contexts where it would be useful to get dates
(specifically, the values of date certs) still in ISO date format but
converted to the local time zone?
zw
On Fri, May 29, 2009 at 12:15 PM, Support <address@hidden> wrote:
Presumably these "display times in local time" changes will also affect
any dates/times output via au and au stdio?
Many thanks for making these changes btw :-)...
Tony.
This has been requested many times - I just now got around to doing
it. You get output like this:
o -----------------------------------------------------------------
| Revision: a12108115b1ba91ab5bc3cb58700f35c93fa18b0
| Ancestor: 31dc9889d2a9a1fecc4acf1abb8703aec3ea9113
| Author: address@hidden
| Date: 27 May 2009, 01:23:19 PM
| Branch: net.venge.monotone
There's command line options and a Lua hook to turn it off and/or
customize the date formatting.
I think "log" is the only command that actually prints dates to the
user -- it would be easy to change any other command that does the
same.
zw
_______________________________________________
Monotone-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monotone-devel