Hi,
Im requesting that someone fix the Create/Apply patch functionality of Subversion. Having spoken to Stefan Küng of TortoiseSVN fame, he mentioned that there are a few problems with the create /apply patch that need fixing on the Subversion side before we can do anything on the TortoiseSVN side. Two specific things come to mind: -UTF-16 support. -Binary format file. The use case is as follows: I have some uncommitted changes in my working copy an added .png binary file, and a modified UTF-16 encoded windows resource-script file (.rc). I want to send changes to a friend for review before committing them to the repo. My friend should just receive the .patch file and be able to apply the patch to get to the same Working copy as is on my system. Right now, I have to think about binary and UTF-16 encoded files, and put those in a zip file. Stefan told me that someone had implemented such functionality in the past - that it did not end up getting used because the diff clients needed changing. Im kind of surprised/disappointed that a reliable patch mechanism does not seem to exist for svn. When I do a commit, the changes are bunched up in some binary format and sent to the server. Can we not capture this kind of data in some text-encoded format, and have the patch program understand the format? Below are some archived posts about Create/Apply Patch http://svn.haxx.se/tsvnusers/archive-2011-05/0012.shtml http://svn.haxx.se/tsvn/archive-2009-04/0197.shtml Best regards, Friedrich Brunzema
