For open source projects (like this one) everyone has read access to the repository, and anyone can make a contribution to the project. So how are those contributions controlled? If just anyone could commit changes, the project would be permanently unstable and probably permanently broken. In this situation the change is managed by submitting a patch file to the development team, who do have write access. They can review the patch first, and then either submit it to the repository or reject it back to the author.
Patch files are simply Unified-Diff files showing the differences between your working copy and the base revision.
First you need to make and test your changes. Then instead of using → on the parent folder, you select →
you can now select the files you want included in the patch, just as you would with a full commit. This will produce a single file containing a summary of all the changes you have made to the selected files since the last update from the repository.
The columns in this dialog can be customized in the same way as the columns in the Check for modifications dialog. Read the section called “Local and Remote Status” for further details.
By clicking on the Options button you can specify how the patch is created. For example you can specify that changes in line endings or whitespaces are not included in the final patch file.
You can produce separate patches containing changes to different sets of files. Of course, if you create a patch file, make some more changes to the same files and then create another patch, the second patch file will include both sets of changes.
Just save the file using a filename of your choice.
Patch files can have any extension you like, but by convention they
should use the
You are now ready to submit your patch file.
You can also save the patch to the clipboard instead of to a file. You might want to do this so that you can paste it into an email for review by others. Or if you have two working copies on one machine and you want to transfer changes from one to the other, a patch on the clipboard is a convenient way of doing this.
If you prefer, you can create a patch file from within the Commit or Check for Modifications dialogs. Just select the files and use the context menu item to create a patch from those files. If you want to see the Options dialog you have to hold shift when you right click.
Patch files are applied to your working copy. This should be done
from the same folder level as was used to create the patch.
If you are not sure what this is, just look at the first line of
the patch file. For example, if the first file being worked on was
and the first line in the patch file is
then you need to apply the patch to the
However, provided you are in the correct working copy, if you
pick the wrong folder level, TortoiseSVN will notice and suggest the
In order to apply a patch file to your working copy, you need to have at least read access to the repository. The reason for this is that the merge program must reference the changes back to the revision against which they were made by the remote developer.
From the context menu for that folder, click on
files are shown, but you can opt for “All files”.
If you previously saved a patch to the clipboard, you can use
in the file
open dialog. Note that this option only appears if you
saved the patch to the clipboard using
Copying a patch to the clipboard from another app will not
make the button appear.
Alternatively, if the patch file has a
.diff extension, you can right click on it
directly and select
In this case you will be prompted to enter a working copy location.
These two methods just offer different ways of doing the same thing. With the first method you select the WC and browse to the patch file. With the second you select the patch file and browse to the WC.
Once you have selected the patch file and working copy location, TortoiseMerge runs to merge the changes from the patch file with your working copy. A small window lists the files which have been changed. Double click on each one in turn, review the changes and save the merged files.
The remote developer's patch has now been applied to your working copy, so you need to commit to allow everyone else to access the changes from the repository.