Ronny Voelker wrote:
> Nathan Kidd <nathan-svn <at> spicycrypto.ca> writes:
>>Subversion/TortoiseSVN 1.2 will have better limiting of how many logs
>>are initially shown...
>
> This workaround applies only, if the initial import is the only revision,
> which has a large number of changed paths. I don't think this is the case.
[snip]
> So, to solve this issue, how about an additional option in the settings dialog:
> 'Default number of changed paths'.
> According to this option, only the first n changed paths per revision
> are displayed by default in the log dialog.
As Simon already mentioned, the server doesn't support requests for
partial path information. So either the server needs a new API (which
seems unlikely to happen) or a new "Show Log" algorithm would be needed.
Some brainstorming ideas:
Idea 1:
A new option /* Nathan dodges Stefan's +6 Bolt of Option-Zapping
Lightning */ applying to the Show Log dialog could be:
"Load changed paths later" (or similar)
Which when selected does a "svn log" instead of "svn log -v".
After displaying the initial results it then automatically does a "svn
log -v" and starts filling out the path structures.
PRO: you get near-immediate feedback, particularly helpful when simply
choosing a revision number (e.g. for merge)
CON: duplicating network/server traffic, paths of recent changes may not
be filled out as quickly
Idea 2:
An alternate approach would be for TortoiseSVN to remember "big"
revisions and "show log -v" around them, till all other revisions are
pulled and then pull the "big" revisions one-by-one.
PRO: Much faster log results shown
CON: Code is more complicated. Need way to reset remembered "big"
revisions in case of repository dump/filter/load.
-Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue May 17 17:30:50 2005