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

RE: continual rebuilds

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-07-29 19:32:37 CEST

"Roger Talkov" <rctalkov@appworx.com> wrote on 07/29/2005 01:25:46 PM:

> I have solved the problem by setting use-commit-times = yes.
> A long time ago, before ever using subclipse, I had problems with
subversion
> when I enabled this, so I kept it disabled. It works fine now

Let me just clarify, because what you write is confusing.

Prior to 1.2 there was a bug in Subversion where if you used the
use-commit-times = yes feature (the default is no) then it created a
working copy that had the status problem I described. Namely, Subversion
correctly set the time on the file according to the commit time, but it
forgot to also update it's .svn/entries file to have the same time.
Consequently, it forced the svn status command to have to do a full
compare of every file.

This was fixed in 1.2, so now you should be able to use either value.
However, if you had a pre-existing working copy, only running the svn
cleanup command, or doing a fresh checkout, would fix the working copy.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Sat Jul 30 03:32:37 2005

This is an archived mail posted to the Subclipse Users mailing list.

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