> Whose local time zone? The server or the client?
>
> >So here's a patch that adds a "-L" option to
> >"cvs log" which causes the dates to be
> >output in the local time zone.
[smc] Ahh, good point. It's the server's.
Doing the client is a little bit harder, but is
of course the correct way. Harder, since it's not safe
to assume the client's representation of time
is the same as the server's, even if you make
the assumption that they both use some kind
of int that contains seconds since sometime
in the past..
Hmm, on second thought, You could convert
the number of seconds diff between localtime
and GMT to ascii string, then send that across
to the server, which sn't really hard. And my patch
_already_ makes the assumption that a time_t is
some kind of int and is in seconds...
Hmm, I haven't looked at what "cvs history -z" does,
which Larry Jones suggested. Maybe it already
does this type of thing...
-- steve
