Angew

Thanks for the reply, @calbzam. If I understand you correctly, this would give me the encoding a file had in a particular revision. I would then have to somehow track that across invocations to find the revision when it changed, right? Also, I need this for all files in the repo which match a specific extension wildcard. It seems a bit overwhelming to do this by revision & file "cross product". Is there perhaps a way to get a changeset's diff in textual or otherwise script-processable form?

I normally do this by creating the review for the entire branch. Then I go through the changesets one after another, looking at each in turn. Before making a comment, I check in the [whole-]branch review whether the piece of code I'm about to comment on was changed further or not.

I need to search my repository for all changesets which changed the encoding of any file (to UTF-8 with BOM, but finding all changesets modifying encoding in any way would be fine for me too). I read through the docs on 'cm find' and related, but couldn't find what to write into the where clause for this. Is it possible to find all such changesets?