Getting the svnmerge-intergrated property right when merging
trunk->py3k->release30 is a little tricky. The most concise set of
instructions I have found which gets it right is to do the following in
the 3.0 maintenance branch after committing to the py3k branch:

svn update
svnmerge merge -r <py3k-rev>
svn revert .
svnmerge -M -F <py3k-rev>
<test change still works, etc>
svn commit -F svnmerge-commit-message.txt

Revert and property changes on "." and running that second svnmerge line
is also useful if you do a "svn update" after the first svnmerge and get
a conflict on the svnmerge-intregrated property. The -M option tells the
utility to only make the property changes, while the -F tells it to go
ahead despite the existence of local modification.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to