Arch manual pages

Determine whether there are commits in <head>..<upstream>
that are equivalent to those in the range <limit>..<head>.

The equivalence test is based on the diff, after removing whitespace and line
numbers. git-cherry therefore detects when commits have been
"copied" by means of git-cherry-pick(1), git-am(1) or
git-rebase(1).

Outputs the SHA1 of every commit in <limit>..<head>, prefixed
with - for commits that have an equivalent in <upstream>, and
+ for commits that do not.

git-cherry is frequently used in patch-based workflows (see
gitworkflows(7)) to determine if a series of patches has been applied
by the upstream maintainer. In such a workflow you might create and send a
topic branch like this:

Here, we see that the commits A and C (marked with -) can be dropped from
your topic branch when you rebase it on top of origin/master,
while the commit B (marked with +) still needs to be kept so that it
will be sent to be applied to origin/master.