> Can you confirm if the following actions sounds plausible: > 1. duplicate current excalibur/thread and pool src content in > cvs to an equivalent svn repository
I believe that you need to move an entire CVS module at a time. > 2. copy/branch/whatever the current excalibur/thread/src to > thread/api and thread/impl and thread/instrumented > (preserving history) and equivalent for pool Yes, svn copy is the right thing. And you might create a tag before doing so, in case someone wants easy access to the current packaging. Tags are just a lightweight copy in Subversion. See http://svnbook.red-bean.com, which is the definitive work on Subversion. > 3. dump the duplicates between api and impl through a normal > removal Not sure what you mean here. > 4. copy over the new content from the current CVS api > impl and instrumented package over the svn content for the > respective directories (generating historical diffs) > 5. commit Yes, you could copy your existing files from your CVS checkout to your SVN checkout, and commit them. You don't have to edit all over again. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
