[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-11-08 17:01:20 CET

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?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 8 17:03:16 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.