summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: ac1a1f9)
raw | patch | inline | side by side (parent: ac1a1f9)
author | Rene Scharfe <rene.scharfe@lsrfire.ath.cx> | |
Thu, 26 Oct 2006 21:32:41 +0000 (23:32 +0200) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 27 Oct 2006 01:53:18 +0000 (18:53 -0700) |
This patch adds the diagram from the long usage string of git-cherry to
its documentation, and documents the third option. I changed some of
the + to - in order to save the reader from wondering where they might
fit into the picture.
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <junkio@cox.net>
its documentation, and documents the third option. I changed some of
the + to - in order to save the reader from wondering where they might
fit into the picture.
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-cherry.txt | patch | blob | history |
index e1bf8ee255e531c1c790ec9f10815f3f972000f8..27b67b81a58956c48452b7aee46b9742ca02e31a 100644 (file)
SYNOPSIS
--------
-'git-cherry' [-v] <upstream> [<head>]
+'git-cherry' [-v] <upstream> [<head>] [<limit>]
DESCRIPTION
-----------
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.
+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