1git-cherry(1) 2============= 3 4NAME 5---- 6git-cherry - Find commits not merged upstream 7 8SYNOPSIS 9-------- 10'git-cherry' [-v] <upstream> [<head>] [<limit>] 11 12DESCRIPTION 13----------- 14The changeset (or "diff") of each commit between the fork-point and <head> 15is compared against each commit between the fork-point and <upstream>. 16 17Every commit that doesn't exist in the <upstream> branch 18has its id (sha1) reported, prefixed by a symbol. The ones that have 19equivalent change already 20in the <upstream> branch are prefixed with a minus (-) sign, and those 21that only exist in the <head> branch are prefixed with a plus (+) symbol: 22 23 __*__*__*__*__> <upstream> 24 / 25 fork-point 26 \__+__+__-__+__+__-__+__> <head> 27 28 29If a <limit> has been given then the commits along the <head> branch up 30to and including <limit> are not reported: 31 32 __*__*__*__*__> <upstream> 33 / 34 fork-point 35 \__*__*__<limit>__-__+__> <head> 36 37 38Because git-cherry compares the changeset rather than the commit id 39(sha1), you can use git-cherry to find out if a commit you made locally 40has been applied <upstream> under a different commit id. For example, 41this will happen if you're feeding patches <upstream> via email rather 42than pushing or pulling commits directly. 43 44 45OPTIONS 46------- 47-v:: 48 Verbose. 49 50<upstream>:: 51 Upstream branch to compare against. 52 53<head>:: 54 Working branch; defaults to HEAD. 55 56<limit>:: 57 Do not report commits up to (and including) limit. 58 59Author 60------ 61Written by Junio C Hamano <junkio@cox.net> 62 63Documentation 64-------------- 65Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. 66 67GIT 68--- 69Part of the gitlink:git[7] suite