I found that I can use git log --left-right --cherry-pick --pretty=raw master...dev | tig --pretty=raw to compare two branches, and the --cherry-pick parameter works well however --left-right still doesn't work.

I've also run into this for -G and -S.

I wonder, why not just pass through all options to git log Or alternatively, have a command which does so? I thought that maybe tig log is exactly this, but e.g. tig log -S foo shows no output, while git log -S foo does, so that does not seem to be what git log is for.

Wait, scratch my comment, that's a different problem. Seems I should specify -Sfoo rather than -S foo, since in the latter case, foo is interpreted as a revision rather than an option. I filed #1040 about improving this.

The options you name, --left-right and --cherry-mark do not really influence which commits git log returns, only how they are displayed. Normally, tig runs git log to decide which commits to show and once you "open" a commit to show details, it runs git show to show it.

It seems that tig is smart enough to also pass --left-right to git show in this case, but that doesn't help, since left/right has no real meaning for a single commit, only relative to other commits.

I would expect --cherry-pick to work, since it omits commits from the output, but I haven't got a good testsetup to test here.