I have used this sequence for handling new projects with svn: - Start a new project in whatever IDE is used - Work a bit on initial code so the framework is OK - Exit the IDE - Command prompt in the parent of the project dir - svn import <project dir name> <svn URL> --depth files -m "message" - rename <project dir> <something else> - svn co <svn URL> <project dir> - move <something else>\<all subdirs> <project dir>\ - delete <something else> - start dev IDE again and hopefully find that it loads properly
I want to avoid having to do all the steps following the svn import command so I can just continue working where I was when I wanted to put the project under version control. Specifically there may be ignored files in the project dir that are needed by the dev IDE but should not be versioned and I would like these to be intact yet not part of the versioning. I have svn ignores in my config file so they won't be part of the import and therefore they will not appear after the following checkout... Is there some flag or such that can help out during the import or in a following checkout so that the extra directory >something else> does not need to be used? Or can I just move the .svn dir from the working copy to the original project and then it will be converted in place? -- Bo Berglund Developer in Sweden
