From the SVN book (emphasis added): The perceptive reader is probably wondering at this point whether the peg revision syntax causes problems for working copy paths or URLs that actually have at signs in them. After all, how does svn know whether news@11 is the name of a directory in my tree or just a … Read more
svn add –force * –auto-props –parents –depth infinity -q Great tip! One remark: my Eclipse adds new files to the ignore list automatically. It may be a matter of configuration, but anyhow: there is the –no-ignore option that helps. After this, you can commit: svn commit -m ‘Adding a file’
Actually, I found an even better way with the –no-ff option on git merge. All this squash technic I used before is no longer required. My new workflow is now as follows: I have a “master” branch that is the only branch that I dcommit from and that clone the SVN repository (-s assume you … 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
What I’ve done in the past is to have a default config file which is checked in to source control. Then, each developer has their own override config file which is excluded from source control. The app first loads the default, and then if the override file is present, loads that and uses any settings … Read more
To find the version of the subversion REPOSITORY you can: Look to the repository on the web and on the bottom of the page it will say something like: “Powered by Subversion version 1.5.2 (r32768).” From the command line: <insert curl, grep oneliner here> If not displayed, view source of the page <svn version=”1.6.13 (r1002816)” … Read more
Indeed, thanks to the comments to my post here, it looks like sparse directories are the way to go. I believe the following should do it: svn checkout –depth empty http://svnserver/trunk/proj svn update –set-depth infinity proj/foo svn update –set-depth infinity proj/bar svn update –set-depth infinity proj/baz Alternatively, –depth immediates instead of empty checks out files … Read more
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
I’ll add my own two cents to this question: I use the following SVN ignore pattern with TortoiseSVN and Subversion CLI for native C++, C#/VB.NET, and PERL projects on both Windows and Linux platforms. It works well for me! Formatted for copy and paste: *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store thumbs.db … 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.