On Wed, 28 Nov 2001 15:40:18 +0000, Trenton D. Adams wrote: > That's retarded. Why not simply use the local computer's time then? > After all, if it's not handling the timezone issue anyhow, why not. > > I'm -7 GMT and it's use +7 GMT. > CVS is an international app - it copes well if you have developers spread across the globe checking out projects, as each person gets the file in their local time. Funnilly enough, NTFS works on GMT too - MS got it right the second time around (then screwed up the conversion to local time... sigh...).
Even if the timezone bias is incorrect on your machine it wouldn't matter because everything would be uniformly incorrect. This used to happen before the DST code was fixed... files would be 1 hour out for 6 months. This also effects every other app on your system (which are still using the broken MS timestamp routines), so people don't really notice (using Explorer try creating a file at a specific time in, say, June, then looking at the file in December - the timestamp will be one hour out). The only way that this could fail is with two machines with one on an incorrect timezone. eg: Machine A is set to GMT-7 Machine B is set to GMT+0 A file is created on machine A at 1pm. This is stored on NTFS as 20:00GMT and stored by CVS 'as is'. The file is then checked out on machine B. CVS stores the timestamp on the filesystem, which doesn't adjust it, as it doesn't have to. The file now appears to have a timestamp of 8pm. Both machines have the correct time on the file with respect to their own settings, however you have just created an international timezone in your office... Tony _______________________________________________ Cvsnt mailing list [EMAIL PROTECTED] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
