This is an old revision of the document!
This page is shamelessly stolen from http://www.psc.edu/~semke/cvs_branches.html//
=====Merging branches=====
====Using Update====
<code>
cvs update -j TagOrBranch1 -j TagOrBranch2 my_module
</code>
The above command will locate the differences between TagOrBranch1 and TagOrBranch2. Of the lines that are different between them, the lines in TagOrBranch2 will be patched, or merged, into the sources in your working directory.
An annoying problem that I have not yet solved is that new files that appear in TagOrBranch2 but not in TagOrBranch1 do not get created by the merge. The only thing I know of to get these files into the new version is to checkout TagOrBranch2, copy the files into the merged working directory, and do
<code>
cvs add filename
</code>
====Using Checkout====
<code>
cvs checkout -j TagOrBranch1 -j TagOrBranch2 my_module
</code>
The above command will locate the differences between TagOrBranch1 and TagOrBranch2. Of the lines that are different between them, the lines in TagOrBranch2 will be patched, or merged, into the latest revision on the main trunk of my_module.
In order to have these differences merged into a different branch, and then have that branch checked out, use
<code>
cvs checkout -r BranchToMergeTo -j TagOrBranch1 -j TagOrBranch2 my_module
</code>
Like update, file that were created between TagOrBranch1 and TagOrBranch2 do not get created automatically.