I am having trouble getting codestriker (1.9.8) to display svn diffs containing newly added empty files as colored diff. The content of the diff file is displayed as is instead.
I don't see any option I can give to svn to have it not putting empty files into the diff. Is there a workaround in codestriker? Or has it been fixed in 1.9.9?
The empty files are baselines for tests that don't generate any output.
I am really surprised subversion is creating diffs like this. Normally even blank files will be properly formatted. I'll add a new test case for this so that 1.9.10 will have this fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok - its been fixed now. If you updated the lib/Codestriker/FileParser/SubversionDiff.pm file with http://codestriker.cvs.sourceforge.net/viewvc/\*checkout*/codestriker/codestriker/lib/Codestriker/FileParser/SubversionDiff.pm?revision=1.14, then all should be well.
This will appear in 1.9.10.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having trouble getting codestriker (1.9.8) to display svn diffs containing newly added empty files as colored diff. The content of the diff file is displayed as is instead.
I don't see any option I can give to svn to have it not putting empty files into the diff. Is there a workaround in codestriker? Or has it been fixed in 1.9.9?
The empty files are baselines for tests that don't generate any output.
Index: empty.txt
Index: more.txt
--- more.txt (revision 0)
+++ more.txt (revision 0)
@@ -0,0 +1 @@
+/* Some content */
I am really surprised subversion is creating diffs like this. Normally even blank files will be properly formatted. I'll add a new test case for this so that 1.9.10 will have this fixed.
Ok - its been fixed now. If you updated the lib/Codestriker/FileParser/SubversionDiff.pm file with http://codestriker.cvs.sourceforge.net/viewvc/\*checkout*/codestriker/codestriker/lib/Codestriker/FileParser/SubversionDiff.pm?revision=1.14, then all should be well.
This will appear in 1.9.10.
Thanks. It works now (with 1.9.8).