| RE: [subversive-dev] Revision Graph |
|
Hello Jesper,
Revision graph caches results for repository, so if you call
graph for any resource from repository then cache will be used. In order to
calculate all copies (branches/tags/trunk) for resource and all related to it
resources we need to log ALL repository.
In next versions we plan to show caches information in
preferences and add ability to manipulate them, e.g. delete, export,
import etc.
From:
subversive-dev-bounces@xxxxxxxxxxx [mailto:subversive-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jesper Skov
Sent: Thursday, April 22, 2010 1:09 PM To: subversive-dev@xxxxxxxxxxx Subject: SV: [subversive-dev] Revision Graph Ah, it does indeed appear to cache the result. Subsequent revision graphs render pretty fast. Super! J Jesper Fra:
subversive-dev-bounces@xxxxxxxxxxx [mailto:subversive-dev-bounces@xxxxxxxxxxx]
På vegne af Jesper Skov Interesting.
Very! But when I opened Revision Graph for a random file, it traverses
*all* revisions on our server. We are close to 100.000 revisions at
present. Obviously, it takes a fair bit of time (64.000 revisions to go at the
moment), so I am not sure I actually get to *see* the result for another
hour or so. Is it not possible to make a log on the resource in question, and
then poll SVN for the specific revisions that have been
involved? If not, I hope the plugin at least caches the result, or I am pretty
sure it is unusable for us
L Cheers, Jesper Fra:
subversive-dev-bounces@xxxxxxxxxxx [mailto:subversive-dev-bounces@xxxxxxxxxxx]
På vegne af Igor V. Burilo Dear Subversive
Users, |