Unexpected conflicts merging updates from trunk to a branch
From: Matthew Pounsett <matt_at_conundrum.com>
Date: Thu, 7 Feb 2013 09:19:47 -0500
I've been running into unexpected tree conflicts when updating branches from the trunk, after reintegrating to the trunk where and file adds or removes were involved in the reintegrate. I expect I'm doing something wrong here, but I haven't been able to figure out what. Can someone point me in the right direction? Here's a simple example that demonstrates my issue.
In this case my server is 1.7.5 and my client is the MacOS client 1.6.17.
~/Development/svn-test > svn update
~/Development/svn-test > cd branches/
~/Development/svn-test/branches > svn cp ^/trunk mybranch
~/Development/svn-test/branches > svn commit -m "created mybranch"
Committed revision 31.
~/Development/svn-test/branches > cd mybranch/
~/Development/svn-test/branches/mybranch > touch foo
~/Development/svn-test/branches/mybranch > svn add foo
~/Development/svn-test/branches/mybranch > svn commit -m "added file foo"
# Not necessary.. just being paranoid for demonstration purposes.
~/Development/svn-test/branches/mybranch > cd ../../trunk/
~/Development/svn-test/trunk > svn merge --reintegrate ^/branches/mybranch
# Again, probably not necessary.
~/Development/svn-test/trunk > svn commit -m "reintegrated mybranch"
Committed revision 33.
~/Development/svn-test/trunk > cd ../branches/mybranch/
~/Development/svn-test/branches/mybranch > svn update
# With this merge I expect to pick up any changes that are the results of
~/Development/svn-test/branches/mybranch > svn status
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.