Hi. (Please CC me since I'm not subscribed.)
I was doing some hacking on the Tailor codebase to provide timezone info
to backends if available, and I noticed that although darcs record --pipe
parses (IOW: does not complain) ISO8601 dates with timezone information,
the value of the offset is not used. Trivial test case:
% darcs --version
1.0.8 (release)
% date --iso-8601=seconds
2006-06-25T14:46:53+0200
% echo test >test.txt
% darcs init
% darcs add test.txt
% echo -e "2006-06-25T14:46:53+0200\nMe.\nFoo.\n" | darcs record --all --pipe
What is the date? Who is the author? What is the patch name? What is the log?
Finished recording patch 'Foo.'
% darcs changes
Sun Jun 25 16:46:53 CEST 2006 Me.
* Foo.
Notice how darcs changes shows a time that is not the one provided to
darcs record, which seems to just have interpreted it as UTC, thus
resulting in an extra 2h offset.
I checked the bug system, and I noticed this is reported in Issue#173,
which has been not commented on for a month now. Please feel free to
forward the above test case to it, since I don't have an account there
(I'm not a regular darcs user, so...)
Finally, I am very very interested in the answer to the following
question:
- once the above gets fixed, if the timezone is different to the local
timezone, eg.:
% echo -e "2006-06-25T05:46:53-0700\nMe.\nFoo.\n" | darcs record --all
--pipe
What will be the output of `darcs changes` (local TZ=CEST):
(a) Sun Jun 25 14:46:53 CEST 2006 Me.
(b) Sun Jun 25 05:46:53 PDT 2006 Me.
Many thanks in advance.
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Listening to: Manolo García - En una playa calma
_______________________________________________
darcs-devel mailing list
[email protected]
http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
