Ok, I figured it out - Pending Changes has always compared - it just
can't open (and I tried F3). This should be added if at all possible,
because then we'd be able to do code reviews that much easier (and
follow our logic).
From: Stephen Kestle [mailto:Stephen.Kestle@orionhealth.com]
Sent: Tuesday, 19 October 2004 11:06 a.m.
Subject: Compare to Base recursive speed
I don't know whether this has been raised before, but when comparing to
base on my source tree, I have to wait a really long (unacceptable)
amount of time to get my results. I suppose it's only unacceptable
because it locks out eclipse.
Anyhow, a list of changed files can be found in about 5-10% of the time
of loading the compare. Does the recursive compare have to compare all
the files before it can even show what's been changed? It's really
annoying having to use tortoise to do these comparisons when the eclipse
one is so much better.
Another solution would be to allow compares from the Show Pending
Changes function. Edit: It seems that show pending changes does do a
compare now - when did this happen?
Is it possible to mirror this functionality to the recursive compare?
(ie, no loading until compare is done)
Received on Tue Oct 19 10:45:43 2004