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

Re: Bug? use-commit-times=yes causes big performance degradation

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-02-02 16:57:58 CET

Norbert Unterberg <nepo@gmx.net> writes:

> Maybe my first mail got lost in hyperspace...

I didn't see it.

> When turning on the use-commit-times setting, working copies which are
> checked out after that become very slow on every status
> fetch. Subversion does a full file compare for all files in the
> working copy.
> What happens is that the files get the checkin time stamp, but the
> time stamps stored in the .svn/entries files are the checkout times.

It's a bug in update_editor.c:install_file.

> This only happens on checkout, updates seems to work correctly.

From the code I would expect update to fail as well.

> Using svn, Version 1.1.3 (r12730) on Windows XP SP2

It's also present on the trunk.

It's possible to "fix" an existing working copy by using a trunk
client to run "svn cleanup", but with a 1.1.x client it's more
difficult. Running "svn revert --recursive" will do it providing you
don't mind any local modifications being reverted. If you want to
preserve local modifications then you need to use "svn commit" and
arrange for the commit to abort. One way to do this is to exit the
log message editor without making changes and then choose "a)bort"
when prompted. Another way is to set SVN_EDITOR to an invalid editor,
e.g. on Unix one can use "SVN_EDITOR=/bin/false svn commit".

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 2 16:59:21 2005

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.