We have various projects all in the same repository. Sometimes a
project won't get worked on for a while which causes quite a large
difference between two successive revisions e.g.
Revision: 2605
Revision: 1806
Revision: 1627
Revision: 1626
Revision: 1625
Revision: 476
Revision: 405
Revision: 347
Revision: 346
Revision: 344
Revision: 343
Revision: 342
Revision: 341
Revision: 340
Revision: 333
The default number of log messages to show is 100. This only lists
2605. The 'Next 100' button (I'm guessing) asks for revisions from
2505. This doesn't return any new history. No matter how many times
you press it, you don't get any more history because the next item is
actually about 700 away. The only solution is to do a get all. But the
idea of the next 100 is because get all can be slow. While the above
example isn't a have repository (yet) it is growing quite quickly in
other ares so soon, show all may be slower than we'd like so the next
100 would be useful.
Could this behaviour be changed? Not totaly sure how, but here are a
couple of ideas:
a) Store the lowest revision it tried to receive and subsequent presses
would try below that (e.g. first press would try from 2505 but none
would appear so second press would try from 2405 etc). At least some
repeated pressing would return new messages eventually.
b) Automatically do the above. If next 100 doesn't return any,
automatically try with 200, then 300 etc.
Or any other ideas you people may have.
Cheers
Russell
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 28 11:33:09 2005