Technically speaking, no history is lost. In practice, these actions are not sufficient. If you have branches, then you may want to somehow replicate some of them to the new location as well. CVS doesn't help with that at all.
Also, if you want to merge between branches in your before- and after-rename source trees, you must go through a lot of steps to create source patches in the old location and install them in the new location. "cvs log" also produces fragemented histories, which are at best glued together with comments that users must remember to enter by hand. In this specific case, munging the modules database might be a higher quality solution for what you want. Note that this action has its own limitations, and thus is also not a general purpose solution to the rename problem. >--- Forwarded mail from [EMAIL PROTECTED] >I have a sub-tree foo and I want to move it from /old/foo to /new/foo >where "old" is a top-level module and "new" is a top-level module. >1. Create a copy of /old/foo in /new/foo using cvs export. >2. Physically remove the files in /old/foo while preserving the CVS >folders. >3. Remove the contents of /old/foo using cvs remove. >4. Add the new files in /new/foo using cvs add. >5. Commit the changes to /new then commit the changes to /old. >Will this preserve my history? >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
