If you already have it checked out locally then you can cd to where it is checked out, then use this syntax: $ svn up -rXXXX ref: Checkout a specific revision from subversion from command line
Git is not better than Subversion. But is also not worse. It’s different. The key difference is that it is decentralized. Imagine you are a developer on the road, you develop on your laptop and you want to have source control so that you can go back 3 hours. With Subversion, you have a Problem: … Read more
I needed this as well, and with the help of Bombe’s answer + some fiddling around, I got it working. Here’s the recipe: Import Git -> Subversion 1. cd /path/to/git/localrepo 2. svn mkdir –parents protocol:///path/to/repo/PROJECT/trunk -m “Importing git repo” 3. git svn init protocol:///path/to/repo/PROJECT -s 4. git svn fetch 5. git rebase origin/trunk 5.1. git … Read more
The claim of why merging is better in a DVCS than in Subversion was largely based on how branching and merge worked in Subversion a while ago. Subversion prior to 1.5.0 didn’t store any information about when branches were merged, thus when you wanted to merge you had to specify which range of revisions that … Read more
Basically you need to “merge backwards” – apply a diff between the current and previous version to the current version (so you end up with a working copy looking like the old version) and then commit again. So for example to go from revision 150 (current) back to revision 140: svn update svn merge -r … Read more
Essentially you have to have admin rights (directly or indirectly) to the repository to do this. You can either configure the repository to allow all users to do this, or you can modify the log message directly on the server. See this part of the Subversion FAQ (emphasis mine): Log messages are kept in the … Read more
One approach would be to: Copy edited items to another location. Delete the folder containing the problem path. Update the containing folder through Subversion. Copy your files back or merge changes as needed. Commit Another option would be to delete the top level folder and check out again. Hopefully it doesn’t come to that though.
Both are very similar but Subversive is the “eclipse svn provider”. I primarily use Subversive because of a few convenient features: Grouping of history When I’m browsing the history of a branch instead of just seeing a bunch of rows for every commit it can group commits by today, week, etc. Mapping of trunk, branches, … Read more
Create a new branch using the svn copy command as follows: $ svn copy svn+ssh://host.example.com/repos/project/trunk \ svn+ssh://host.example.com/repos/project/branches/NAME_OF_BRANCH \ -m “Creating a branch of project”
(This answer has been updated to match SVN 1.8 and 1.9’s behaviour) You have 2 questions: Marking files as ignored: By “ignored file” I mean the file won’t appear in lists even as “unversioned”: your SVN client will pretend the file doesn’t exist at all in the filesystem. Ignored files are specified by a “file … Read more