Why is this entry still listed as active? it has been implemented already, see https://blog.plasticscm.com/2018/11/unified-diff-of-branch.html and "cm patch".

Any updates on this one? This is a really important feature for me since I often have to review refactorings with hundrets of files. (e.g. method signature has changed). These are actually minor changes but with many files being changed. Back in subversion I was just reading the revision's unified diff scrolling through the changes and checking whether greater refactorings have been made here and there. This was done in 5 minutes, now I review half an hour because I have to click through each and every file!
Setting up a command line diff tool for these operations is not an option for me. I need a one click solution without the need to reconfigure my client.

Yes, please add a feature to create a path file from a change set or even a range of change sets, or a branch. Its just a button "create patch file" from diff view and a command. :)

A command to output the changed lines, in unified diff format, to console. (I do not know what unix diff format is.) A patch command is unnecessary, it is part of MinGW.

Just export a patch

Yes, patch command please

This will eventually lead to patch, so it is definitely a requirement.

Do you think this would help:
http://plasticscm.uservoice.com/forums/15467-general/suggestions/4007214-option-to-select-diff-tool-on-the-command-line

ie. 'cm diff --tool=diff'

Yes, and patch.