[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN Log dialog does not update correctly

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 23 Feb 2012 21:43:54 +0100

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:
>>
>> [snip]
>>>
>>> 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
>> zero.
>>
>> 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
>> 1.7.4
>
>
> 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
> refreshes.
> 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.
http://code.google.com/p/tortoisesvn/issues/detail?id=222

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2925994
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-02-23 21:44:16 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.