RE: Re: Re: Re: Re: [Subclipse-users] Branch merge issues
From: Stephen Colebourne <scolebourne_at_joda.org>
Date: Wed, 27 May 2009 05:34:45 -0700 (PDT)
> Here is an example that shows the eligible revs from the Subclipse
I ran this (from the directory of the working copy of the branch, although I doubt that matters). I got back the correctly filtered list of revisions after the revision I indicated was merged.
> > I've tried it with the svn:mergeinfo only on /branch1, and on /branch1/eclipseprojecta and
Yes, those were basically the commands I ran (where MAXREV was the revision just after cvs migration). I don't understand why you say they would need to be fully syched before doing this. According to the svn 1.5 online manual, all this does is block these revisions from being considered. (ie. I'm happy to not have any svn merge features for versions before my MAXREV).
> Finally, keep in mind that SVN automatically knows the "natural
Does that mean that the svn:mergeinfo needs to start at rv1000 in your example?
What would be useful info for you to find out what the issue is here?
Stephen
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
|
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.