blob: b0468aa746a074741de8b4a4ebeb82c177edb1e8 [file] [log] [blame]
Junio C Hamano1a4e8412005-12-27 08:17:231git-cherry(1)
2=============
3
4NAME
5----
Junio C Hamano01078922006-03-10 00:31:476git-cherry - Find commits not merged upstream
Junio C Hamano1a4e8412005-12-27 08:17:237
8SYNOPSIS
9--------
Junio C Hamanoa053d542006-10-27 09:29:1310'git-cherry' [-v] <upstream> [<head>] [<limit>]
Junio C Hamano1a4e8412005-12-27 08:17:2311
12DESCRIPTION
13-----------
Junio C Hamano1bb569e2006-05-05 23:14:2514The changeset (or "diff") of each commit between the fork-point and <head>
15is compared against each commit between the fork-point and <upstream>.
16
Junio C Hamanoff4b4312006-10-25 22:55:3117Every 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
Junio C Hamano1bb569e2006-05-05 23:14:2520in the <upstream> branch are prefixed with a minus (-) sign, and those
Junio C Hamanoa053d542006-10-27 09:29:1321that 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
Junio C Hamano1bb569e2006-05-05 23:14:2537
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
Junio C Hamano1a4e8412005-12-27 08:17:2344
45OPTIONS
46-------
47-v::
48Verbose.
49
50<upstream>::
51Upstream branch to compare against.
52
53<head>::
54Working branch; defaults to HEAD.
55
Junio C Hamano16f98872007-06-12 16:09:1456<limit>::
57Do not report commits up to (and including) limit.
58
Junio C Hamano1a4e8412005-12-27 08:17:2359Author
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---
Junio C Hamano35738e82008-01-07 07:55:4669Part of the linkgit:git[7] suite