<p>Using the svnmerge.py tool it is possible to merge between branches, up and down.  It is hard to find the details for doing this.  Hopefully, v1.5 will have a neat method for doing this without using svnmerge.py - details requested!</p>

[{'answer_id': 68512, 'author': 'readonly', 'author_id': 4883, 'author_profile': 'https://Stackoverflow.com/users/4883', 'pm_score': 3, 'selected': True, 'text': '<p>It looks like you\'re asking about 1.5 merge tracking.  Here\'s a quick overview for doing merges to/from trunk (or another branch): <a href="http://blog.red-bean.com/sussman/?p=92" rel="nofollow noreferrer">http://blog.red-bean.com/sussman/?p=92</a></p>\n'}, {'answer_id': 68554, 'author': 'casualcoder', 'author_id': 10578, 'author_profile': 'https://Stackoverflow.com/users/10578', 'pm_score': 0, 'selected': False, 'text': '<p>With svnmerge.py, you initialize both branches (when going in one direction, you only need to initialize one of the branches).  Then merge using the -b (For bidirectional flag).  Here is a summary starting from branch one to branch two.  $REPO is the protocol and path to your repository.</p>\n\n<blockquote>\n  <p>svn copy $REPO/branches/one $REPO/branches/two \\<br>\n  -m "Creating branch two from branch one."<br>\n  svn checkout branches/one one<br>\n  svn checkout branches/two two</p>\n  \n  <p>cd one\n  svnmerge init ../two<br>\n  cd ../two<br>\n  svnmerge init ../one  </p>\n</blockquote>\n\n<p>You may now edit both branches.  Changes from one to two can be merged by:</p>\n\n<blockquote>\n  <p>cd two<br>\n  svnmerge merge -b -S one<br>\n  svn commit -F svnmerge-commit-message.txt  </p>\n</blockquote>\n\n<p>Conversely, changes from two to one can be merge by:</p>\n\n<blockquote>\n  <p>cd one<br>\n  svnmerge merge -b -S two<br>\n  svn commit -F svnmerge-commit-message.txt  </p>\n</blockquote>\n\n<p>Be sure to note the -b flag!</p>\n'}]
['https://Stackoverflow.com/questions/68448', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/10578/']