If you have an SVN branch on which a huge of amount of work has been done, effectively being the mai开发者_如何学运维n place for development, is there any special way to decide this branch should become the trunk? A project I'm involved with has this situation, it's kind of like taking a branch of your operating-system code and then replacing the entire kernel.
Is there a 'right' or 'wrong' way to handle this? It seems forcing a branch to merge when it's very different doesn't achieve much, if all the trunk changes have been merged to your branch.
Why not just merge everything back to trunk?
Or if you could (in a single transaction, preferably):
- Delete the existing trunk.
- Copy (or rename) the branch to trunk.
Using svnmucc you could do:
svnmucc rm http://host/repos/trunk cp HEAD http://host/repos/branches/b http://host/repos/trunk
精彩评论