git-cherry(1)
=============
NAME
----
git-cherry - Find commits not merged upstream
SYNOPSIS
--------
'git cherry' [-v] [ [ []]]
DESCRIPTION
-----------
The changeset (or "diff") of each commit between the fork-point and
is compared against each commit between the fork-point and .
The commits are compared with their 'patch id', obtained from
the 'git patch-id' program.
Every commit that doesn't exist in the branch
has its id (sha1) reported, prefixed by a symbol. The ones that have
equivalent change already
in the branch are prefixed with a minus (-) sign, and those
that only exist in the branch are prefixed with a plus (+) symbol:
__*__*__*__*__>
/
fork-point
\__+__+__-__+__+__-__+__>
If a has been given then the commits along the branch up
to and including are not reported:
__*__*__*__*__>
/
fork-point
\__*__*____-__+__>
Because 'git cherry' compares the changeset rather than the commit id
(sha1), you can use 'git cherry' to find out if a commit you made locally
has been applied under a different commit id. For example,
this will happen if you're feeding patches via email rather
than pushing or pulling commits directly.
OPTIONS
-------
-v::
Verbose.
::
Upstream branch to compare against.
Defaults to the first tracked remote branch, if available.
::
Working branch; defaults to HEAD.
::
Do not report commits up to (and including) limit.
SEE ALSO
--------
linkgit:git-patch-id[1]
Author
------
Written by Junio C Hamano
Documentation
--------------
Documentation by Junio C Hamano and the git-list .
GIT
---
Part of the linkgit:git[1] suite