[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: Chia-liang Kao <clkao_at_clkao.org>
Date: 2005-05-09 01:11:04 CEST

Peter N. Lundblad <peter <at> famlundblad.se> writes:
> > 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?

I think you can that the repos_history to respect return value
from the callback, which you store the limit in baton. this seems
more general and is what I had:



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 9 01:19:40 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.