https://prod.jnet.julianscorner.com/ 2026-04-17T14:45:50+00:00 https://prod.jnet.julianscorner.com/ https://prod.jnet.julianscorner.com/_media/wiki/dokuwiki-128.png text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://prod.jnet.julianscorner.com/programming/svn/mergerevision Revert to a Previous Revision 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. text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://prod.jnet.julianscorner.com/programming/svn/repo-ignorefiles Configure SVN to Ignore Build Outputs and User Setting Files Build outputs and User settings should not be put into source control. To prevent this, you can configure SVN to ignore certain types of files and folders: Using TortoiseSVN * Open Windows Explorer. text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://prod.jnet.julianscorner.com/programming/svn/repo-org Organization within "The Repository" There are two ways of creating Repositories. One way is to create a different repository for each project. That's fine so long as you want to manage multiple repositories... My preference is to have one repository know by me as text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://prod.jnet.julianscorner.com/programming/svn/structure Structure Of "The Repository" This is the basic structure of any of my Subversion repositories: / |-- PROJECT NAME (or Abbreviation) | |-- branches | |-- tags | `-- trunk |-- PROJECT NAME (or Abbreviation) | |-- branches | |-- tags | `-- trunk