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

Re: Early warning: Major log cache code update

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-10-05 11:18:48 CEST

On 10/5/07, Simon Large <simon.tortoisesvn@googlemail.com> wrote:
> On 05/10/2007, Stefan Küng <tortoisesvn@gmail.com> wrote:
> > On 10/5/07, Stefan.Fuhrmann@etas.de <Stefan.Fuhrmann@etas.de> wrote:
> > > To do before merging into /trunk:
> > >
> > > * Refresh in log dialog shall update the head revision
> > > (e.g. "any new revisions?") as well as update authors and
> > > comments in the revisions shown.
> >
> > I think to update authors/comments, the users can use the 'clear log
> > cache' in the settings dialog. A refresh in the log dialog should not
> > invalidate the cache IMHO.
> 'Clear log cache' is very destructive as it clears the the caches for
> all repositories at once. A way to refresh one repository, or just the

There's an issue open about that (not clearing everything but only for
selected repositories).

> current view would be useful. Apart from updating to a newer HEAD,
> isn't this the only other natural use for the refresh button?

Most users only refresh to see if there are new commits available,
*not* to refresh the cache (heck, most users won't even notice that we
cache stuff now, apart of course from the speedup).
I suggest that to refresh the cache, we don't do this with a normal F5
but maybe with a Ctrl-F5 refresh - otherwise only check for new


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 5 11:18:54 2007

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.