RE: CVS Server times
David A. Bartmess wrote: 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). Just FYI... So, are you saying that cruisecontrol relies only on the timestamp of the repository file to determine what has changed? This seems a little crude - if I apply a tag to a file, that will change its timestamp, but not the contents. No rebuild should be required. Anyway, let me elaborate on your scenario slightly to see if I understand you. Client-server protocol is not being used (if a client/server protocol is being used, then all timestamps would be relative to the server's clock, and the client's clock is irrelevant). Clients mount a server's directory locally, and the mounting system sets the timestamp on the file according to the client's system clock. Cruisecontrol looks only for newer files (not just files whose timestamp changes). Sounds like the answer is: if you're using cruisecontrol, or if you have workstations in multiple time zones, use client/server protocols instead of mounting the repository locally. This would be good security advice in any case - I really don't like users having direct access to the repository. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: CVS Server times
Guus Leeuw jr. wrote: *All* CVS Client - Server and Server - Client communication is (virtually) done in UTC. I think David's point was that CVS itself will work well, but be careful of any add-ons - they may not work as expected. At least, that's how I interpreted his message. And it's a good reminder. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS Server times
On Thursday 24 February 2005 11:33 pm, Guus Leeuw jr. wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:info-cvs- [EMAIL PROTECTED] 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 I was talking about the 5 minute difference in my example, though. Not in the timezone difference. Rakesh asked about a difference in time. That could have weird consequences, depending on the usage on checkout... -- David A. Bartmess Software Configuration Manager / Sr. Software Developer eDingo Enterprises http://edingo.net _ jSyncManager Development Team (http://www.jsyncmanager.org) jSyncManager Email List (https://lists.sourceforge.net/lists/listinfo/jsyncmanager-devel) But one should not forget that money can buy a bed but not sleep, finery but not beauty, a house but not a home, medicine but not health, luxuries but not culture, sex but not love, and amusements but not happiness. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: CVS Server times
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. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS Server times
rakesh mailgroups writes: does anyone know if the repository server having a different time than local PCs will cause issues with CVS? It shouldn't. -Larry Jones I can do that! It's a free country! I've got my rights! -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS Server times
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). Just FYI... -- David A. Bartmess Software Configuration Manager / Sr. Software Developer eDingo Enterprises http://edingo.net _ jSyncManager Development Team (http://www.jsyncmanager.org) jSyncManager Email List (https://lists.sourceforge.net/lists/listinfo/jsyncmanager-devel) But one should not forget that money can buy a bed but not sleep, finery but not beauty, a house but not a home, medicine but not health, luxuries but not culture, sex but not love, and amusements but not happiness. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: CVS Server times
-Original Message- From: [EMAIL PROTECTED] [mailto:info-cvs- [EMAIL PROTECTED] 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 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
