If you change the above example to use `git diff-tree -cc` instead, then the explanations from the `diff-tree` docs may be more appropriate:

> --cc
> This flag changes the way a merge commit patch is displayed, in a similar way to the -c
> option. It implies the -c and -p options and further compresses the patch output by
> omitting uninteresting hunks whose the contents in the parents have only two variants
> and the merge result picks one of them without modification. When all hunks are
> uninteresting, the commit itself and the commit log message is not shown, just like in
> any other "empty diff" case.

and

> -c
> This flag changes the way a merge commit is displayed (which means it is useful only
> when the command is given one <tree-ish>, or --stdin). It shows the differences from
> each of the parents to the merge result simultaneously instead of showing pairwise diff
> between a parent and the result one at a time (which is what the -m option does).
> Furthermore, it lists only files which were modified from all parents.

I don't know if these explanations from `diff-tree` are better or worse. The `log` ones are actually somewhat more concise, but if you switch the blog post to use `diff-tree`, obviously it will be confusing to display docs from `log` instead...