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

Re: log-cache not updated after editing log message

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-06-21 11:00:16 CEST

On 6/21/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 cahced 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.
> I don't know if it's a good idea, but it could be a starting point.
> The problem is that either the server or every client would have to update
> the property upon an edit of a svn:log property. Server could be easier via
> a post-revprop-change hook, but this would exclude file:// URLs.

Lübbe, you need a vacation! :)
Your suggestions get more complicated every day...
(and when your back from your vacation, read this suggestion again -
then you'll know my answer to this).


  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 Thu Jun 21 11:49:28 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.