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