Mark,
> That said, it is entirely possible that the latest changes in US laws > about when the Daylight Savings Time is changed may require that the > file be updated. If that were the case then I would have expected to see more discussion about it on the TortoiseCVS, WinCVS and CVSNT newsgroups - which I haven't. The changes to the DST laws simply altered 'when' the change occurs (which changes every year in Australia and many other countries so has been tested every year since 2004 outside the US). I really can't see this as being an explanation - unless the CVS 1.11 changes were never complete - I do suppose most windows users use CVSNT. If Nelson can test using CVSNT and if the result is that CVSNT doesn't have the problem and CVS 1.11 does - then it's a concrete place for someone to begin looking ;) Of course the explanation could be non-DST related. I've seen this 'every file stamp wrong' problem when CVS is used with some anti-virus software, also if the client and server clocks are sufficiently non-synchronised it'll occur too. Regards, Arthur
