On 8 April 2011 13:34, yangxinghua <yangxinghua_at_gmail.com> wrote:
> Dear all:
> Thanks for your help and patience for reading!!!(I am not a native speaker, so forgive my expressions if anything confused you)
No problem, lot's of readers are non native speakers as well.
> I am new here for asking a question about tortoiseSVN working so slowly when it is used to check for modifications
> My computer's hard disk is used to be 160G(there are 2 disks, one contains C,D,E,F partitions and the other contains K,L partitons)
> It is changed to 1T size now, and contains C,D,E,F partitions(which is made by ghost clone). The former files on K,L partitions are copied two directories(F:\K1 & F:\L1 for example, there are working copies in these two directories) on F
> However, I do find one problem, that is, using the check for modifications menu in the K1 or F1 directory gets really slow speed, almost more than 40 minutes is spent when the check for modifications finishes! OMG~~
> BUT, if I checkout a new working copy in the same directory, the check for modifications only spends 2~3 minutes to get the result?
> Anyone could help me and teach me the reason???
This has probably got to do with the way subversion tries to guess
which files may have been changed. One way is to look at the last
change timestamps. These probably got messed up by making the copy
from K and L to F:\K1 and F:\L1. Did you try to do an update or
cleanup on the working copies? That may reset the timestamp checks. If
it does not help, a fresh checkout will solve it for you (as you
. @@ // \\ "De Chelonian Mobile"
. (_,\/ \_/ \ TortoiseSVN
. \ \_/_\_/> The coolest Interface to (Sub)Version Control
. /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-08 17:46:05 CEST