[cvsnt] Re: uptodate checks failed

Bo Berglund Bo.Berglund at system3r.se
Wed May 25 16:25:38 BST 2005


In this situation the cvs update command sometimes still leaves the file
as locally modified, but if you do a cvs status on the file it usually
(=always) clears the flag if the files are identical.

/Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of teknokrat
Sent: den 25 maj 2005 16:03
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: uptodate checks failed


Tony Hoyle wrote:
> teknokrat wrote:
> 
>>
>> Hang on, but this has happened when there are no diffreneces between 
>> the files and the versions locally and remotely are identical. Also, 
>> why should clean timestamps have any effect?
> 
> 
> 'up to date check' is entirely based on version numbers as far as the 
> client is concerned.
> 
> As clean timestamps is an eclipse thing I'd ask there why it makes a 
> difference - maybe it's just a 'cvs update'?
> 
> Tony

This appears to happen when the user has changed a file and changed it 
back so eclipse thinks the file has been altered but it is still 
identical to the file in the repository. I agree that this appears to be 
an eclipse specific thing.
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt



More information about the cvsnt mailing list