RE: Converting a branch into the main trunk

[Chuck . Irvine]

You don't say what the purpose of the trunk is; it's probably your
stable baseline. That being said, I would recommend that you do things
in the typical way, i.e. merge the branch into the trunk. If the branch
is very different than the trunk, then CVS should do the right thing,
i.e. make the trunk "look" like the branch. If your branch represents a
nearly complete rewrite of your application, then large parts of your
original application will essentially get merged away. My best advice is
to experiment a lot with CVS if you are somewhat new to it, but in
general you can trust it to "work" correctly.

-----Original Message-----
From: Chris.Deever [mailto:address@hidden
Sent: Tuesday, November 07, 2000 7:31 AM
To: info-cvs
Subject: Converting a branch into the main trunk


When merging a development branch into the HEAD trunk, is it possible to
somehow insure that code development branch always overwrites the main
trunk
completely?

Since CVS does a line by line diff comparison to determine what code to
merge, I'm a bit hesitant to do the merge since the two versions of code
are
very different at this point.  I'd like to know that the code in the
development branch will always take precedence over code in the HEAD
trunk.

Maybe there is a way to simply rename the branches?

Thanks,

Chris

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs