Simon Large <slarge <at> slarge.plus.com> writes:
> A better option would be to find a way of speeding up the display of
> 20,000 changed paths, but I don't think there is anything obvious to do
> here.
Hey, I've just noticed, that you have solved this issue with r3387.
The user experience is much better now, thanks. :)
> But, it doesn't help with getting the data from the repository. SVN
> doesn't provide any way to limit the number of changed paths it returns.
> The --limit feature in SVN 1.2 is used to limit the number of revisions
> returned, not the number of paths.
I like Nathan's and Mark's suggestion, to retrieve the list of changed paths on
demand.
It seems to be against the philosophy of having as less network traffic as
possible, but in fact it may result in lesser network traffic in the day-to-day
usage.
Every time I'm viewing the log, the changed paths for _all_ displayed revisions
are transferred over the network, but mostly I’m not interested in the changed
paths of _all_ revisions, but only of some specific revisions. Most of the
changed path information is transferred over the network and then thrown away.
Viewing the log of my test-repository (20 revs, 4 revs with >10000 changed
paths) over a dial-up connection is impossible with the recent log dialog
(because of the amount of data to be transferred), but would be possible with
'lazy loading' of the changed path data.
Ronny
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon May 30 15:03:24 2005