Re: git cherry doesn't list a merge commit

Tajti Ákos [off-list ref] writes:

However, the manual of git cherry says:
"*Every* commit that doesn’t exist in the <upstream> branch has its
id (sha1) reported, prefixed by a symbol. The ones that have
equivalent change already in the <upstream> branch are prefixed with a
minus (-) sign"

The sole purpose of the command is to decide which commits in the existing
history to run "format-patch" on to feed the output to "am" to update the
other history, and it was clear for both readers and the author of the
documentation that a "commit" meant a "non-merge commit" in that context.

A patch to rephrase it to "every non-merge commit" for clarity may not be
useless, though.