From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 13 Feb 2012 18:57:17 GMT
Subject: Re: git cherry doesn't list a merge commit
Message-ID: <7vaa4mfto2.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4F392976.9070009@intland.com>

Tajti Ákos <akos.tajti@intland.com> 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.