git-cherry man page on Cygwin

Man page or keyword search:  
man Server   22533 pages
apropos Keyword Search (all sections)
Output format
Cygwin logo
[printable version]

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

NAME
       git-cherry - Find commits not merged upstream

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

DESCRIPTION
       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>
		     /
	   fork-point
		     \__+__+__-__+__+__-__+__> <head>

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

		      __*__*__*__*__> <upstream>
		     /
	   fork-point
		     \__*__*__<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.

OPTIONS
       -v
	   Verbose.

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

       <head>
	   Working branch; defaults to HEAD.

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

SEE ALSO
       git-patch-id(1)

GIT
       Part of the git(1) suite

Git 1.7.9			  02/13/2012			 GIT-CHERRY(1)
[top]

List of man pages available for Cygwin

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net