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.
suppose you update your code to revision 10 which is broken. You want to go back to revision 9, work on the code and wait until someone will fix the build:
svn merge -rHEAD:9 .
But it won’t work, why?
If you simply want to go back to an other revision,
updateis what you are looking for:You can work on the code but you can’t commit changes. Well, if revision 10 didn’t change the same file you changed, you could commit but it’s better if you wait for revision 10 to be fixed.
Instead, if you want to go ahead and work on the code, you might consider to create a branch from revision 9, go ahead in the branch and reintegrate the branch into trunk when revision 10 is fixed.