Newbe Dev Stack

Answer : svn merge -r 854:853 l3toks.dtx or svn merge -c -854 l3toks.dtx The two commands are equivalent. Check out "undoing changes" section of the svn book sorry to use up some space on just a reiteration of the previously given answer - but this is something I always end up in trouble with. Let's say I've updated the local files to the latest revision, which is 854. Then, I'd want to get an older revision - the version of the file from few revision earlier, say revision 851. Copy would work: svn copy -r 851 svn+ssh://<repository URL>/l3toks.dtx ./l3toks.dtx .. however, I can't be bothered grepping for the repo URL :) Update seemingly might work: svn up -r 851 ./l3toks.dtx ... however, it also marks the local copy as "freshly checked out", or rather "same as online revision" (i.e. in Tortoise/RabbitVCS you get a green OK checkmark) - which means you cannot do svn ci -m "rolled back to r 851" : simp...

Answer : I've had a few issues applying SVN generated patches with git. I'd recommend applying any subversion patches directly with patch command, and use git to verify that said patch was successfully applied. $ patch -p0 < xxx_parser.patch $ git diff @emcconville answer works if you have patch as an executable command in the command line. For others: Go to the svn repo svn diff --git >> gitFormat.patch From your (Copy this file to the) git repo git apply gitFormat.patch

Answer : You can use the Snippet Generator for General SCM step. This displays the familiar Subversion configuration options, and takes credentials as parameter as usual. The Snippet Generator will produce a tad ugly representation of your parameter selections and looks something like this: checkout([$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[credentialsId: '34761a89-1402-47d7-96e2-aec22ffdc50b', depthOption: 'infinity', ignoreExternalsOption: true, local: 'cable_branch', remote: "https://trac.nci.org.au/svn/cable/branches/$SVN_...

Answer : Given that the Apache Subversion server will be moved to this new DNS alias: sub.someaddress.com.tr : With Subversion 1.7 or higher, use svn relocate . Relocate is used when the SVN server's location changes. switch is only used if you want to change your local working copy to another branch or another path. If using TortoiseSVN, you may follow instructions from the TortoiseSVN Manual. If using the SVN command line interface, refer to this section of SVN's documentation. The command should look like this: svn relocate svn://sub.someaddress.com.tr/project Keep using /project given that the actual contents of your repository probably won't change. Note: svn relocate is not available before version 1.7 (thanks to ColinM for the info). In older versions you would use: svn switch --relocate OLD NEW Grepping the URL before and after might give you some peace of mind: svn info | grep URL URL: svn://svnrepo.rz.mycompany.org/repos/trunk/DataPortal ...