Re: log-cache not updated after editing log message

On 21/06/07, Lübbe Onken <l.onken@rac.de> wrote:
> Hi Simon,
>
> You wrote:
>
> > I think I saw reference to an enhancement which would provide a hook
> > for changing cached messages, such that if you edit a log message or
> > author, the local cache gets updated. Of course this can only work on
> > the machine where the details were edited.
>
> Would be nice to have, but otoh it's not the most common use case. To inform
> other users you need a push service from the server and this would only help
> people who are subscribed to a commit mailing list.
>
> I wonder if you could use a property like tsvn:changedlogmessages on the
> repository root to store the numbers of changed log messages and a timestamp
> for each change. The log cache could look at this property, check which
> messages have new changes and poll them again. This list would grow over
> time and could become quite unwieldy.

Log caching is a client-side convenience which only works in TSVN.
Getting special tsvn: props and server hooks to make this work will be
highly unpopular on public servers which are accessed using many
different clients.

That's why I also suggest a context menu entry to update a single log
message in the cache from the server. Easy (for Stefan + Stefan^2 :)
to do and no server side impact.

It might also be beneficial to have per-repository cache clearing
rather than one button to clear all log caches at once. But the same
could be said of clearing authentication, commit log messages, etc.

Simon

-- 
       ___
  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