Troy Curtis Jr wrote:
> So you are working along making commits to "task_branch". Eventually
> you merge all your changes (or some subset) from the "task_branch"
> back into "trunk", complete with the svnmerge maintained property
> (svnmerge-integrated). It turns out your changes fix an issue that
> exists in the "release 1.0 branch" so you dutifully merge the changes
> from "trunk" to "release 1.0 branch". The trouble is, that revision
> on trunk contains a modification to the 'svnmerge-integrated' property
> because it was performed with svnmerge, but *this* svnmerge operation
> ALSO modified svnmerge-integrated and so it produces a conflict.
Use the latest svnmerge.py on trunk -- this bug has been fixed.
Cheers,
Raman Gupta
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 26 01:31:53 2007