Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve created a repo, and then I ran svn import . https://myrepo. It seems to have checked everything in nicely, and I can check it out on my other machine. However, it doesn’t seem to create the .svn folder, so I can’t run any svn ci commands at a later date.
This creates massive headaches to try and sync up later, because now all my stuff is already in the repo, but it conflicts with the changes I’m trying to commit.
What am I doing wrong?
I never use import because it’s uncomfortable. Import doesn’t create .svn directories, you’ll have to run an additional checkout of the newly imported directory.
Instead of importing files I first create an empty directory in the repo and check it out into my existing project’s directory that I want to “import”. Then you can simply run commit and it’ll add all files.