NOTE: if you don't know what this is talking about, you probably have not your own Subversion server and this answer may be not useful for your case. Let's also assume that your user is called svn like in the above example. The filesystem structure should be something like this: $ ls -la /repoĭrwxrwx. But it may be /home/svn/myrepo or something like that. Identify your repository on your serverįirst of all identify your repository on your server's filesystem. In the case you are a Subversion system administrator (with command line access) and you have to revert a very big mistake (for example, someone committed something that should not be committed for no reason in the world), and if you want to try to completely drop a commit at any cost, even at the risk of destroying the repo: Step 1. Note that the svn merge command reverts a commit in the sense of having another commit undoing your changes, but keeping your wrong commit in the history.

R in place of interfaces/AngelInterface.php in all the above. Svn commit -m 'reverted -r22060' interfaces/AngelInterface.phpĪlternatively I could do the same thing on a directory, by specifying. Mv interfaces/AngelInterface.php~ interfaces/AngelInterface.php Then :- mv interfaces/AngelInterface.php interfaces/AngelInterface.php~ So I can svn update -r 22059 interfaces/AngelInterface.php and I end up with code as it was in -r22059 again. svn log interfaces/AngelInterface.php shows my change as r22060 and the previous commit on that file was r22059. I made changes to the file, committed them, updated the build computer ran the phpdoc compiler and found my changes were a waste of time. In my particular case my target is interfaces/AngelInterface.php.

Seems to work, but isn't permanent (my svn is simply showing an old revision). I tried the above, ( svn merge) and you're right, it does jack.

Snailsvn