Saving svn changes for use on another computer? or backup unchanged svn

Question

Say I made changes to some files, but I do not want to check them. I want to save the changes in a batch file or in some archive, and then send them to other developers / ourselves / etc. that they can take a look at my changes and apply them to their working copy. Can this be done?

Simplified scenario

Can you back up unmanaged svn changes?

Answer 1

If you just want to show them the changes that they can apply, you can create a patch .

svn diff > patchfile

If you have already done this, you can create a patch between different versions .

For example, to create patch changes from 341 to the latest version:

svn diff -r 341:HEAD http://svn.example.com/repos/calc/trunk > patchfile

Answer 2

Of course, use svn diff to grab a copy:

 svn diff >modifications.patch 

This creates a patch file, which can then be moved to another computer and applied there:

 patch -p1 <modifications.patch 

Please note: if the remote computer has a working copy for another version of the Subversion repository, you may have conflicts when applying the patch. The patch program has a different conflict resolution process than Subversion itself.

Answer 3

If you are not sure that you are doing a trunk transaction, you can create a branch and commit it and tell other developers to check this branch to see your changes.
When everything is in order, you can combine it with the trunk.

Answer 4

I used a product called Code Collaborator , which can lead to a manual exit from your process. This is a code checking tool that integrates with SVN as well as other version control systems. You create a review, add your uncommitted modified files to it, invite others to the review, and they see the difference between your version and what is in the repository. Keep in mind this is an expensive tool, but in my experience it was worth it. A thirty day demo is available if you try it.