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

Re: [Subclipse-dev] Revision graph status and plan

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 27 Aug 2008 16:58:39 -0400

On Wed, Aug 27, 2008 at 1:34 PM, Alberto Gimeno <gimenete_at_gmail.com> wrote:

> I've committed a little change. Now the merge information is stored,
> but not shown in the graph yet. I store just the first nesting level.
> I'm using a "level" integer to know in which nesting level I am, and I
> ignore any log message deeper than level=1
> The implementation works with any value of "includeMergedRevisions".
> If "false" it simply won't know anything about merge information.
> I'm going to try to include the information in the graph output.

On Subversion's own repository, this command essentially never ends:

svn log -g -rHEAD:0

Until the API gives us more control, I wonder if we could do things
differently to get a performance compromise? For example, maybe we
could just build the cache we do now, and provide a context option on
a revision node to get the mergeinfo "on demand" for just that
revision? This could update the cache for next time.

We could also maybe do it on demand as the graph is built, but that
would make performance really inconsistent.

I think we need to figure out some kind of way to defer getting the
information. Ideally the cache can still be updated when we do get it

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-08-27 22:58:52 CEST

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