Re: svn status: does not notice changed file if timestamp of "new" file is older

maybe the date comparison logic is screwed? which file is it in?

on svn status, it maybe notices it, but there is definitly no output.

on svn up, it compares "not equal", but then it overwrites the file
in the working copy, and not the other way round (merge).

i think you can only use date comparison for speeding up the
comparison, but never judge the contents of a file by "this file has
newer date than the other".

-------------------------------------------------------
From: Ben Collins-Sussman <sussman@collab.net>
Date: 08 Nov 2002 10:01:20 -0600
Content-Type: text/plain; charset=us-ascii
Subject: Re: svn status: does not notice changed file if timestamp of
"new" file is older

solo turn <soloturn99@yahoo.com> writes:

> svn v14.5(r3578) on w2k seems to have a defficiency when you copy a
> changed file from another drive into the svn working copy.
>
> this must be an issue with file date/times. newly checked out, the
> file gets a new timestamp. if you copy a file with an older
timestamp
> it thinks it is not modified, which is of course wrong (different
> timestamt = chances are good that also the contents is different).

Hmm, looking at the code, I'm not sure what's wrong.

The function svn_wc_text_modified_p() compares the timestamp on the
working file against the timestamp recorded in the entries file. If
they're identical, it assumes no change.

So I don't see how this could be happening: a timestamp that's
younger than the one recorded in the entries file should still
compare
as "not equal".

Can anyone else reproduce?

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 12 11:18:46 2002