Re: Create/Apply Patch - UTF-16 and binary support
From: Friedrich Brunzema <brunzefb_at_yahoo.com>
Date: Wed, 22 May 2013 13:12:00 -0700 (PDT)
yes, lack of UTF-16 is one of the issues. The other is creating / applying patches for binary files.
By the sounds of it, this is not really a burning issue for the project - ie not on your roadmap.
Question is - how useful would this functionality be to end-users? Maybe using a .zip program to ship changes
to a fellow developer is just as easy - are these non-trival svn changes worth the effort is what I'm asking, I guess.
Still, conceptually I'm kind of bothered by the fact that svn has the functionality, but that it does not work reliably for all file types.
If it does not work reliably, is it even worth having the create patch/apply patch functionality? [Just putting the question out there...]
Stefan K- One could try to tackle this problem on the TortoiseSVN side. Have a new Create Zip patch - functionality looks for changed wc files,
zips all of them using the correct hierarchy from the working copy. Patch could just overwrite in a dumb way, or could actually try to merge
what it can. Or you don't provide a patch function at all, but leave unzipping to the end-user. Still, this sounds like a bad hack.
If one were to try tackling this problem and fixing it the 'right way' (and I'm not saying I necessarily would), where would one start?
From: Stefan Sperling <email@example.com>
To: Friedrich.Brunzema <firstname.lastname@example.org>
Cc: email@example.com; firstname.lastname@example.org
Sent: Wednesday, May 22, 2013 1:50:45 PM
Subject: Re: Create/Apply Patch - UTF-16 and binary support
On Wed, May 22, 2013 at 12:29:16PM -0400, Friedrich.Brunzema wrote:
> I’m kind of surprised/disappointed that a reliable patch mechanism does not
> seem to exist for svn.
Well, before Subversion 1.7, there was no support for applying patches at all!
I think the basic problem you're asking about is that Subversion
does not support UTF-16 as a text format. This problem isn't specific
to the 'svn patch' command. Solving this problem probably isn't trivial.
This is an archived mail posted to the Subversion Dev mailing list.