Version: (using KDE KDE 3.5.5) Installed from: RedHat RPMs Running kompare on two directories, it correctly displays both changed and new files (i.e. a file missing in one tree and present in the other). However, if a patch generated with a recursive diff (e.g. 'diff -r -u') and passed to kompare, then only the changed files are displayed, not the new files. Viewing the patch file with less, the contents of the new files are very clearly present. For some reason kompare is skipping over those parts of the patch file and not displaying them. This means that kompare can be used to view the changes in an arbitrary patch file, but the user has to then read the patch file once again with something else (e.g. less), to be sure not to miss any sections that create new files (i.e. that didn't exist previously). It would be better if kompare displayed all parts of the patch file.
Oops sorry, the patches weren't actually created with 'diff -N -r -u'. They were created with something else that doesn't include a correct timestamp in the diff headers. So this is not your problem. SORRY!
Reopening. Kompare should not be so pedantic about the timestamp in the header. If it is there it should use it, if not it should ignore the timestamp but definitely not ignore the entire patch.
It looks like this has been fixed since it works for me.