[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with timezone change in the log output

From: Mark D. Baushke
Subject: Re: Problem with timezone change in the log output
Date: Thu, 29 Jul 2004 09:05:05 -0700

Hash: SHA1

Thomas Singer <address@hidden> writes:

> My name is Thomas Singer and I'm the core developer of SmartCVS.
> A user reported me, that parsing the output of the log command does
> not work correctly with GNU CVS >= 1.12.9. I know, there are always
> user requests (at least in the CVSNT mailing list) to show all dates
> in local timezone. But I don't fully understand, why the CVS *server*
> should report the date in local timezone (which needs to be told the
> CVS server before). The conversion from UTC to the local timezone can
> be handled very easily at client side.

You may wish to checkout a copy of the mainline CVS sources as there has
been a patch to the 'cvs log' and 'cvs ls' code since 1.12.9 was released:

| * Thanks again to Bart Robinson <address@hidden>, `cvs log' & `cvs
|   ls' now actually output local times when the server is version 1.12.9
|   or greater and the client is version 1.12.10 or greater.

The time is sent via output_tagged with a "date" tag in UTC. It is up to
the client to convert it locally which is done correctly in and
will be visible in 1.12.10 at such time as that version is released.

btw: Time is being output in ISO 8601 format "2004-07-29 09:00:00 -0700"
or "2004-07-29 16:00:00 +0000" instead of "2004/07/29 16:00:00" so you
may need to deal with paring dates with a timezone if you are not
already doing it in SmartCVS.

> BTW, I very much would appreciate, if the CVS could produce
> fully-parsable log output, e.g. by escaping special characters in the
> commit messages.

I am not exactly sure what you mean. If you have suggestions that you
can express in terms of a patch to the cvs sources with tests to be
added to sanity.sh, they might be adopted.

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]