.\" Title: git-cherry
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.73.2
.\" Date: 10/09/2007
.\" Manual: Git Manual
.\" Source: Git 1.5.3.3
.\"
.TH "GIT\-CHERRY" "1" "10/09/2007" "Git 1\.5\.3\.3" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
git-cherry - Find commits not merged upstream
.SH "SYNOPSIS"
\fIgit\-cherry\fR [\-v] [] []
.SH "DESCRIPTION"
The changeset (or "diff") of each commit between the fork\-point and is compared against each commit between the fork\-point and \.
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:
.sp
.RS 4
.nf
__*__*__*__*__>
/
fork\-point
\e__+__+__\-__+__+__\-__+__>
.fi
.RE
If a has been given then the commits along the branch up to and including are not reported:
.sp
.RS 4
.nf
__*__*__*__*__>
/
fork\-point
\e__*__*____\-__+__>
.fi
.RE
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\.
.SH "OPTIONS"
.PP
\-v
.RS 4
Verbose\.
.RE
.PP
.RS 4
Upstream branch to compare against\.
.RE
.PP
.RS 4
Working branch; defaults to HEAD\.
.RE
.PP
.RS 4
Do not report commits up to (and including) limit\.
.RE
.SH "AUTHOR"
Written by Junio C Hamano
.SH "DOCUMENTATION"
Documentation by Junio C Hamano and the git\-list \.
.SH "GIT"
Part of the \fBgit\fR(7) suite