On Thu, Feb 23, 2012 at 21:19, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 23.02.2012 15:32, Andreas Tscharner wrote:
>> On 23.02.2012 14:55, Stefan Küng wrote:
>>> You can try this yourself:
>>> if you set that timeout to zero, then as you expected the F5/Refresh
>>> in the log dialog would work as you expected it.
>> Thank you for your explanation. The timeout is (and always was) set to
>> As long as the revision numbers are
>> new = old + 1
>> everything is fine. If it is
>> new> old + 1
>> the update will not be made.
>> I noticed this behavior today a few times. It worked correctly in TSVN
> first of all, there were no changes at all which would affect the log dialog
> or the log cache between 1.7.4 and 1.7.5.
> Also, I just tried this myself, not just with one commit between refresh but
> multiple commits as well (up to 10 commits). I've also tried committing from
> another computer just to be sure the cache wasn't accessed in between
> All this worked just fine for me: the refresh always fetched the log entries
> from the new HEAD revision.
But anyway: I've opened issue #222 for this.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-02-23 21:44:16 CET