Feature Request: Revision graph speed & cached info

I have recently moved from WinCvs to tortoisesvn and the feature I miss most
is the revision graph. I know this feature exists in tortoisesvn, but it is
very slow for large repositories.

I was wondering if the feature could be improved by caching all the revision
graph info locally. I think each file I graph requires that all changes be
sent from the server (from 0 to the HEAD). Could we not cache all the
changes (up to a particular revision) locally and when I graph, it gets all
the newer changes only.

This would mean that 1) speed is significantly improved when graphing
multiple files and 2) I can "update" the graph overnight and then when I do
work the next day I only need to get the most recent changes. Also, the
local info can be indexed in such a way as to speed up the graphing.

Local hard-drive space is cheap, so why not use it to cache the changes of a
repository.

I may be totally off the mark with this suggestion.

Cheers
Gavin

-- 
View this message in context: http://www.nabble.com/Feature-Request%3A-Revision-graph-speed---cached-info-tf3180512.html#a8825558
Sent from the tortoisesvn - dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org