We have a product that is made up of a lot of third party open source modules (Apache, Perl, IMAP, etc.). We want to upgrade to the latest version of these modules.
Typically we would do this by importing the latest version of these modules into our repository. However, I don't see this as a seamless process. I expect to see some modules that are not as stable as others and will have to be reverted to an earlier version (but a later version than what was originally in CVS). Is there a way to do this? Additionally, we have various customizations to the existing stuff on the trunk. When I have done an import in the past, the imported stuff shows up on the trunk after the import. This is not what I want since this is where we are getting the current product from. Is there a way to import to a branch so the person doing the importing can import and check in modifications to this branch without affecting the trunk until the new stuff is ready to be merged? I am not talking about vendor branches here (I don't think.) -- Stephen Rasku E-mail: [EMAIL PROTECTED] Senior Software Engineer Web: http://www.pop-star.net/ TGI Technologies _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs