[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2006-07-15 17:23:38 CEST

On Sat, 2006-07-15 at 09:09 -0500, Ben Collins-Sussman wrote:
> 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.

Ben, your answer is boilerplate, and suggests that you didn't completely
read or understand Vincent's message. The proposal is not to scan every
file's contents on each out-of-date check, but it take into account the
inode change time on Unix (as we apparently once did, years ago).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 15 17:25:06 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.