On 04/19/2013 12:47 PM, C. Michael Pilato wrote: >>> I found that this can be done with the svn command line tools. However, >>> --force must be used. Without --force, svn will see that the file has >>> svn:mime-type prop set to application/octet-stream and refuse to do >>> anything to a binary file. >> >> I nearly suggested this earlier, but my testing failed because I didn't know >> about the --force override! I think I'll file an issue against svnbook to >> point this out. That is, if it's not there already and I've simply >> forgotten that fact in the time since I documented it. :-) > > For those that care: > https://code.google.com/p/svnbook/issues/detail?id=194 > > You know, in light of the fact you can use the runtime configuration to > establish the constant use of an external diff tool, it seems that it would > be beneficial to have another configuration knob that means "My external > diff tool can handle binary files, too, so please assume --force mode > thankyouverymuch." > > Any opinions from the users@ readership on that idea?
I got pretty much no feedback on this, but I liked the idea enough to implement it anyway. In r1478826, I introduced a new 'diff-ignore-content-type' runtime configuration option (which defaults to 'no'). Unless the feature is booed out of existence by the Subversion dev community, it should appear in Subversion 1.9. -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Enterprise Cloud Development
signature.asc
Description: OpenPGP digital signature