Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On Wed, 21 Mar 2007 07:28:32 -0700, "Brandon Frost" <bfrost at hcgsoftware.com> wrote: >Yes, I am in the USA. > >I thought about this as a cause and I suppose it is possible. However, the >time has only been adjusted by 1 hour. I tested this problem on files that >were committed last week and was still getting the issue. If the time/date >stamp on the files caused this problem, you'd think the problem would only >last for 1 hour and then resolve itself on each file. > >Regardless, as soon as I cycled the services, the problem disappeared on all >files. Thanks for your suggestion. > That was just a shot in the dark, really.... But I have also seen this behaviour using an older version of CVSNT on the server and a non-matching also older CVSNT client. But not as old as 2.0.58... This issue went away after CVSNT upgrades but I don't remember when. HTH /Bo (Bo Berglund, developer in Sweden)