by adrian » Tue Oct 28, 2008 11:50 am
Hi,
Unfortunately the client will always refresh the entire working copy at each start as this is required to determine the local status of all files in the working copy.
I'm guessing the working copy is on a machine at the office and not on the local machine where the SVN Client is running, otherwise it shouldn't have taken so long to refresh it. If my assumption is incorrect and your working copy is on your local machine, give us more details as there might be a different problem.
Subversion working copies are larger than working copies of other version control tools because they also keep a base revision. This implies some extra overhead when dealing with the working copy, but this has been considered acceptable by the original designers since the working copy is assumed to be local(fast access).
What I'm trying to explain is that even if the working copy refresh in question would be skipped, you would still need to synchronize/update the working copy sooner or later and since the working copy is not local, it would still take a lot of time to perform these other operations.
In short, I would recommend using a local working copy and a branch for committing unfinished work from office/home to be able to continue that work from either location by simply updating from that branch.
We are thinking about disabling refresh at start-up and simply refreshing the Working copy tree as you expand, but this is more of a running idea as it implies changing the functionality of a lot of working copy actions.
Do not hesitate to contact us if you require further assistance.
Regards,
Adrian Buza
Syncro SVN Client support
Adrian Buza
Syncro SVN Client
http://www.syncrosvnclient.com