[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: [Subclipse-users] Branch merge issues

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 27 May 2009 13:51:18 -0400

On Wed, May 27, 2009 at 1:45 PM, Stephen Colebourne
<scolebourne_at_joda.org> wrote:
>> > Here is an example that shows the eligible revs from the Subclipse
>> > trunk that can be merged to the Subclipse 1.4.x branch.
>> >
>> > $ svn mergeinfo --show-revs=eligible
>> > http://subclipse.tigris.org/svn/subclipse/trunk/subclipse@HEAD
>> > http://subclipse.tigris.org/svn/subclipse/branches/1.4.x/subclipse@HEAD
> OK. So, if I run from the command line:
> svn mergeinfo --show-revs=eligible http://repo/svn/base/trunk/eclipseprojecta@HEAD http://repo/svn/base/branches/1.0/eclipseprojecta@HEAD
> I get an accurate set of results near instantly.
> However, if I run from the command line:
> svn mergeinfo --show-revs=eligible http://repo/svn/base/trunk@HEAD http://repo/svn/base
> /branches/1.0/eclipseprojecta_at_HEAD

The command I'd be looking for here is:

svn mergeinfo --show-revs=eligible http://repo/svn/base/trunk@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.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-05-27 19:51:30 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.