Larry Jones wrote:
Todd Denniston writes:
Will there be an option I can put in my _ environment _ so all CVS commands
client will show UTC times?
Most systems honor $TZ.
darn, I was hoping I could have everything else work with the local $TZ and
cvs would use something like $CVS_TZ
Todd Denniston writes:
Will there be an option I can put in my _ environment _ so all CVS commands
client will show UTC times?
Most systems honor $TZ.
-Larry Jones
That gives me a FABULOUS idea. -- Calvin
___
Info-cvs mailing list
Larry Jones wrote:
Mark D. Baushke writes:
CVS keeps time in UTC to allow for clients that may be in other
timezones. It is always in UTC. User input of dates defaults to
local time, but you may add a timezone explicitly to the datestamp
if you wish.
The feature release of CVS
This has been talked about several times, so I said part 44! :)
However something still does NOT make sense to me..
My sandbox and server are BOTH on the EST time zone, at least when
I say date I get the EST time. However, when I issue a CVS command
(tag, commit, etc.) on the server, the server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
This has been talked about several times, so I said part 44! :)
However something still does NOT make sense to me..
My sandbox and server are BOTH on the EST time zone, at least when
I say date I get the EST time.
Mark D. Baushke writes:
CVS keeps time in UTC to allow for clients that may be in other
timezones. It is always in UTC. User input of dates defaults to
local time, but you may add a timezone explicitly to the datestamp
if you wish.
The feature release of CVS (1.12.x) generally displays
