At this point, realize what is happening: Subversion is calculating the changes between revision 73 and revision 68 of the trunk and applying them to your working copy. Step 2 actually performs the merge (you'd do this after you're happy with the dry run). If you want to see exactly what changes will be applied, do a diff: Step 1 will perform a dry run and show you what the merge will produce. svn commit -m "Reverted to revision 68.".So, for example, if you want to revert the trunk of your application from revision 73 to 68, you would do the following: To revert to a previous version of your application (roll back changes) in Subversion, you merge the changes from your current revision back to the revision you want to revert to. Here, then, is a very simple, plain English explanation of how to revert to a previous version of your application in Subversion, to help anyone who may be starting out with it and is lost. Alas, there is a revert command in SVN, but instead of reverting to a previous revision, it works to undo any local changes you've made to your working copy. When I was first starting out with Subversion, I thought there would be a revert command that took a revision as an argument and basically rolled back your application to revision X. You would think that reverting to a previous version of your application would be one of the key use cases for a version control system like Subversion and that it would be trivial to do, but it's actually not intuitive at all. ![]() ![]() ![]() How to revert (roll back) to a previous revision with Subversion
0 Comments
Leave a Reply. |