On 23 February 2012 13:55, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> 2012/2/23 Andreas Tscharner <andy_at_vis.ethz.ch>:
>> On 23.02.2012 09:25, Stefan Küng wrote:
>>
>> [snip]
>>> That's by design. Refreshing only refreshes the entries shown.
>>
>> Has this always been like this? I think I remember that I could click
>> "Refresh" to check if there are any new commits on this branch or the
>> trunk...
>
> It depends: there's a log cache and a timeout.
> Settings dialog->log caching->timeout in seconds before updating the
> HEAD revision.
>
> If you haven't set that to zero, then you have to wait for the timeout
> before a simple F5/Refresh in the log dialog would fetch the new HEAD
> revisions.
> Only a Ctrl-F5/Refresh will clear the log cache (and therefore the
> timeout as well) and re-fetch everything, including the new HEAD
> revision.
>
> 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.
I can understand the timeout preventing server round-trips when you
invoke the log dialog many times, but if you specifically ask for a
refresh, wouldn't you expect one to happen anyway?
Simon
--
: ___
: 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=2925900
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-02-23 15:13:04 CET