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

Re: Quick analysis of svn log --limit

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-05-08 20:34:50 CEST

On Sun, 8 May 2005, Greg Hudson wrote:

> A potentially better change would be to rewrite svn_repos_get_logs3 to
> not use svn_repos_history at all. The new design would use the
> svn_fs_history interface directly. It would create a history object for
> each provided path, and would step through them in parallel to produce a
> sequence of revisions, stopping when it hits the limit. I think that
> would require the least amount of I/O work.
That's the solution I've had in mind for some time... I like it. You need
a pair of iteration pools per path, don't you?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 8 20:27:21 2005

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.