In D14755#167774, @epriestley wrote:Happy to accept that if you want to double-check that it works and send me a diff for it.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Dec 13 2015
Dec 13 2015
Now that I think of it, the simplest possible way to get the desired effect (return 0 if diff succeeds, 1 if it does not succeed), is to use:
dim added inline comments to D14755: Preserve the exit code of the diff command in binary_safe_diff.sh.
Dec 12 2015
Dec 12 2015
Right, I think I have found the cause. The binary_safe_diff.sh does not preserve the exit code of diff, and it returns 0 even if diff returned 1. Apparently returning 0 causes Subversion 1.9 to emit the file headers again.
dim retitled D14755: Preserve the exit code of the diff command in binary_safe_diff.sh from to Preserve the exit code of the diff command in binary_safe_diff.sh.
For me this gives:
Hmm, this seems to be caused by Subversion 1.9 (which is the default in the FreeBSD ports collection). If I use Subversion 1.8 to run the svn diff --depth empty --diff-cmd '/usr/local/lib/php/arcanist/scripts/repository/binary_safe_diff.sh' -x -U32767 foo.txt command, the output is:
Adding Eitan, since he's our Phabricator wrangler.
I think the problem is because of Subversion automatic properties. For the FreeBSD Subversion repository, automatic properties get added, like this: