Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

GIT-CHERRY(1)                                    Git Manual                                    GIT-CHERRY(1)

       git-cherry - Find commits not merged upstream

       git cherry [-v] [<upstream> [<head> [<limit>]]]

       The changeset (or "diff") of each commit between the fork-point and <head> is compared against each
       commit between the fork-point and <upstream>. The commits are compared with their patch id, obtained
       from the git patch-id program.

       Every commit that doesn't exist in the <upstream> branch has its id (sha1) reported, prefixed by a
       symbol. The ones that have equivalent change already in the <upstream> branch are prefixed with a
       minus (-) sign, and those that only exist in the <head> branch are prefixed with a plus (+) symbol:

                      __*__*__*__*__> <upstream>
                     \__+__+__-__+__+__-__+__> <head>

       If a <limit> has been given then the commits along the <head> branch up to and including <limit> are
       not reported:

                      __*__*__*__*__> <upstream>
                     \__*__*__<limit>__-__+__> <head>

       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 <upstream> under a different commit id. For
       example, this will happen if you're feeding patches <upstream> via email rather than pushing or
       pulling commits directly.


           Upstream branch to compare against. Defaults to the first tracked remote branch, if available.

           Working branch; defaults to HEAD.

           Do not report commits up to (and including) limit.


       Part of the git(1) suite

Git 1.8.3                                        05/24/2013                                    GIT-CHERRY(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.