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

Early warning: Major log cache code update

From: <Stefan.Fuhrmann_at_etas.de>
Date: 2007-10-05 02:33:16 CEST

Hi @all,

under /branches/LogCacheEnhancement, I developed a number of
Improvements that I would like to merge into /trunk. My plan
is to do that some time between 2007-10-06 00:00 and 12:00 UTC.

As a "vital" part of the code gets touched (see below), there
may be blocking errors in it. Please speak up if you want the
merge to be deferred.

Changes done so far:

* Log cache files are ~20% smaller now
* Log cache can be saved and loaded ~30% faster
* Log caches now support merge tracking information and
  user-defined revision properties
* Log caches now support partial information (e.g. merge info
  not available for a given revision)
* Log caches can now be updated, including partial update
  (e.g. only the author of a given revision)

-> Existing log caches can not be used and will be overwritten

* Changing author or comment in the log dialog will update
  the log cache as well.

* Repository properties (root URL, UUID, one path-head-pair)
  are now cached as well
* Log dialog and revision graph use the repository property
  cache to elimilate most server-roundtrips.
* Head revision info is cached for the last queried path only
  and is considered valid for 5 minutes (registry setting
  HeadCacheAgeLimit:DWORD in seconds).

* Minor fixes.

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.

To do after merging into /trunk:

* Mimik svn_client_log4() to actually fill the cache with
  user-defined revprops and to pass them back to the application.
* Decide what to do with the merge info given the limitations
  of the current SVN client API.

-- Stefan^2.
Received on Fri Oct 5 02:33:29 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.