info-cvs
[Top][All Lists]
Advanced

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

RE: CVS Server times


From: Guus Leeuw jr.
Subject: RE: CVS Server times
Date: Fri, 25 Feb 2005 07:33:25 +0100

> -----Original Message-----
> From: address@hidden [mailto:info-cvs-
> address@hidden On Behalf Of David A. Bartmess
> Sent: vendredi 25 février 2005 06:53
> 
> On Thursday 24 February 2005 08:24 am, Jim.Hyslop wrote:
> > rakesh mailgroups wrote:
> > > does anyone know if the repository server having a different time than
> > > local PCs will cause issues with CVS?
> >
> > None whatsoever. CVS was designed to be able to operate with
> workstations
> > in multiple time zones (unlike, say, Visual Source Safe). All times are
> > converted to UTC before being stored in the repository.
> 
> But if a local PC was used to work on files, having a current time at
> checkin
> of 11:30 MDT, and the server at time of checkin is 13:35 EDT, this could
> seriously screw with any automation that relies on the datetime stamp to
> know
> if a build has already included that change (i.e., cruisecontrol).

Uhm?

EDT != UTC && MDT != UTC

*All* CVS Client -> Server and Server -> Client communication is (virtually)
done in UTC. Meaning, as Jim said, local PC uses MDT, talks to CVS server,
and CVS server converts to UTC, and also CVS server uses UTC, talks to CVS
client, and CVS client converts to MDT. The EDT settings of your server are
totally unimportant within the CVS server!

<proud>
We (as in previous job) used to manage a CVS repo in Germany, and access it
from within the States. No problems in timing *ever* occurred.
</proud>

Cheers,
Guus

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005
 



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005





reply via email to

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