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

RE: Re: Re: Re: Re: Re: [Subclipse-users] Branch merge issues

From: Stephen Colebourne <scolebourne_at_joda.org>
Date: Thu, 28 May 2009 00:49:30 -0700 (PDT)

> The command I'd be looking for here is:
> svn mergeinfo --show-revs=eligible http://repo/svn/base/trunk@HEAD
> http://repo/svn/base
> /branches/1.0_at_HEAD
> Note how eclipseprojecta was removed from both. This is the command
> we'd execute to get the eligible revisions to merge for all projects.

Here are the results for the svn mergeinfo on the command line:

/trunk to /branches/branch1 - quick, correct info for all projects

/trunk/project to /branches/branch1/project - quick, correct info for one project

/trunk/project to /branches/branch1 - slower, wrong as expected (all revisions since branch created)

/trunk to /branches/branch1/project - quick, very slow (~2 minutes), wrong as expected (all revisions from rv1)

Based on this, I really believe that the evidence points to Subclipse issuing the wrong command (the fourth one above). But why for me and not for you? Perhaps you could create a build with extra logging?

Also I don't see why you wouldn't issue the svn mergeinfo at the level of each of the projects, and union the set of returned revision numbers, as doing it at the base level returns rv numbers that don't affect the selected projects.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-05-28 09:49:48 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.