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

Re: Blame caching (was Re: Case study: Mono switches to Subversion)

From: Marcus Rueckert <darix_at_web.de>
Date: 2004-11-18 19:43:42 CET

On 2004-11-18 11:59:07 -0500, Michael Sweet wrote:
> Couldn't you just cache and update (as needed) the last blame results
> in the WC, i.e. add a "blame-base" subdirectory in the .svn directory
> which stores the last results of "svn blame" along with the then-current
> revision.

i thought about something similar for log caching but i would use
~/.subversion/cache/<reposuuid>/log/<file for each log message>

the log messages are maybe stored as xml or in the usual format from
svn. so a client would cache the log messages when running svn up and
svn log could check the cache before asking the repos. similar stuff
could be done for svn blame.

for the log caching it would be usefull to enable it per working copy. i
dont think it has to be enabled by default. but where should the
information about the flag be stored? in the WC?

just my 2 cents


irssi - the client of the smart and beautiful people
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 18 19:44:00 2004

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

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