.\" ** You probably do not want to edit this file directly ** .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Instead of manually editing it, you probably should edit the DocBook XML .\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .TH "GIT\-CHERRY" "1" "09/19/2007" "Git 1.5.3.2" "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 .nf __*__*__*__*__> / fork\-point \\__+__+__\-__+__+__\-__+__> .fi If a has been given then the commits along the branch up to and including are not reported: .sp .nf __*__*__*__*__> / fork\-point \\__*__*____\-__+__> .fi 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" .TP \-v Verbose. .TP Upstream branch to compare against. .TP Working branch; defaults to HEAD. .TP Do not report commits up to (and including) limit. .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