Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Greetings, I apologize for the long post. I'm a new user to CVS, and when I initially set up my repository I made the mistake of importing a 'module' (directory: oldname-2.2) with a version number stuck on the end. I know, bad. I've learned now about tagging and branching. I'm trying to come up with a plan to fix this while keeping the existing built-up history. Given that the module represents thousands of files (it's a dynamic website), I can't use the recommended copy/add/delete/remove procedure. I had hoped to attack this at the repository level. Thanks in advance for any suggestions or advice you have! - Ben === Here are the steps I plan to take. Do these look right, or am I missing something? 1) commit all developers changes to repository and release on each developers machine > cvs release -d oldname-2.2 2) Backup existing repository and put in a safe place. 3) search and replace oldname-2.2 -> newname in CVSROOT/history There appears to be "special" lines in this file: O3cc9d09e|username|<remote>/*0|oldname-2.2||oldname-2.2 Which appear to represent the cvs checkout command (one line for each developer). I think I'd do the same on these lines, replace: oldname-2.2 with: newname in both cases, but I'm not sure. Are there other places in the repository that the project name would show up? A search of the entire repository searching for oldname-2.2 in files turns up only the entries in the CVSROOT/history file. I guess I was expecting it to be in other places too? 4) move the actual directory: oldname-2.2 -> newname > mv oldname-2.2 newname 5) Issue an rtag command to set the proper version/release tag based on a date in the past (when the module was initially created): > cvs rtag -D "2002-04-25" 2_2_Release newname _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs