I think my working copy was pre 1.2, but am not sure. We started using
subversion prior to 1.0, and I'm not sure when I tried using
use-commit-times = yes. I would prefer to use the commit times, as it is
more meaningfull. I did a fresh checkout after setting use-commit-times =
yes.
I'll have our other developers do a cleanup.
Thanks
Roger Talkov
AppWorx
425-644-2121 x135
-----Original Message-----
From: Mark Phippard [mailto:MarkP@softlanding.com]
Sent: Friday, July 29, 2005 10:33 AM
To: users@subclipse.tigris.org
Subject: RE: continual rebuilds
"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.
____________________________________________________________________________
_
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat Jul 30 04:04:53 2005