I believe newer versions of opengrok will do this if you enable the history 
cache in java db.

I know it works for mercurial, but not sure if it is implemented for subversion 
(if not IT shouldnt be hard to add support for subversion)

Trond

Sent from my iPad

On 30. apr. 2010, at 09.04, Patrick ALLAERT <patrickalla...@php.net> wrote:

> Hi list,
> 
> It appears that while updating, the *entire* "svn log" is taken every
> time. This is extremely time consuming on very big projects (>1 000
> 000 commit like KDE or even PHP with ~300 000).
> Would it be possible to only fetch what's missing ?
> The following scenario should be possible:
> 
> 1. New project added
>  a) Entire svn log fetched.
>  b) Storing last revision seen ( => lastRevisionNumberSeen).
> 2. Project source being updated (svn update)
> 3. OpenGrok update:
>  a) If lastRevisionNumberSeen != actual one: svn log --xml -r
> BASE:lastRevisionNumberSeen
>  b) Storing last revision seen ( => lastRevisionNumberSeen).
> 
> Altenatively, an "OpenGrok update" could take care of the update of
> the repository.
> 
> Thanks for you help.
> 
> Kind regards,
> -- 
> Patrick Allaert
> ---
> http://code.google.com/p/peclapm/ - Alternative PHP Monitor
> _______________________________________________
> opengrok-discuss mailing list
> opengrok-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

Reply via email to