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

Re: svn doesn't report modified file when timestamp has not changed

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-07-15 16:09:34 CEST

On 7/13/06, Vincent Lefevre <vincent+svn@vinc17.org> wrote:
> Subversion assumes that if the mtime value has not changed, then the
> file of a working copy has not changed.

Yes, this is a deliberate choice. Both CVS and Subversion examine
current mtime, and compare it to a previously-recorded mtime to decide
if further investigation (filesize comparison, brute-force comparison)
is necessary. If CVS and Subversion didn't have this algorithm, then
commands which scan the working copy (like 'svn status' and 'svn
commit') would be orders of magnitude slower.

> For instance, the commands "recode" and "mv" don't change the
> mtime by default

Don't do that. Use 'svn mv', not 'mv'.

> This is a rather nasty bug, as some changes may remain unnoticed,
> and therefore, they may be lost.

I don't understand, can you elaborate? Where's the risk of data loss?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 15 16:09:59 2006

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.