Hi.
In the following scenario the log window's 'next 100' operation
reloads the same, already loaded set of revisions instead of loading the
next 100 ones:
1. Reproduced using the 'http://svn.boost.org/svn/boost/trunk'
repository, revision [79869].
2. Run the Blame operation on the file:
'tools/build/v2/build/project.py'.
3. Move to line 121 (act-as-jamfile rule). It should be listed as
last modified in revision 18557 by vladimir_prus. (not sure
4. Choose the 'Show log' option from the left frame popup menu for
that line. A log window should open and it should hold information about
revisions 22800 to 79867.
5. Press the 'Next 100' button and all the already displayed log
messages will get duplicated, a single one for revision 22799 will get
added and the log window will now report displaying information about
revisions 22799 to 79867.
6. Repeated 'Next 100' button presses seem to add more duplicates and
not load any additional.
The same does not occur when opening a log window for the same file
directly from Windows Explorer or when using a different line in the
blame window containing a more recent change. It could be that it needs
to be based on a revision that is not initially displayed by the log
window as it does not fit in the 'last 100 revisions' range.
Tortoise SVN version information:
> TortoiseSVN 1.7.7, Build 22907 - 64 Bit , 2012/05/15 12:16:05
> Subversion 1.7.5,
> apr 1.4.6
> apr-utils 1.3.12
> neon 0.29.6
> OpenSSL 1.0.1c 10 May 2012
> zlib 1.2.7
Hope this helps.
Best regards,
Jurko Gospodnetić
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2996741
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-05 11:36:22 CEST