X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=Documentation%2Fgit-cherry.txt;h=893baaa6f656616b2151c572450e037fabee7622;hb=74237d6236d7e32f69469ff26df3f3bb3875f523;hp=9a5e37186fcd03972d490e2e996ce8b078112bbb;hpb=7be14b49ac14da65764a115d7cb64c8a72ab5b61;p=git.git
diff --git a/Documentation/git-cherry.txt b/Documentation/git-cherry.txt
index 9a5e3718..893baaa6 100644
--- a/Documentation/git-cherry.txt
+++ b/Documentation/git-cherry.txt
@@ -11,11 +11,20 @@ SYNOPSIS
DESCRIPTION
-----------
-Each commit between the fork-point and
is examined, and compared against
-the change each commit between the fork-point and introduces.
-Commits already included in upstream are prefixed with '-' (meaning "drop from
-my local pull"), while commits missing from upstream are prefixed with '+'
-(meaning "add to the updated upstream").
+The changeset (or "diff") of each commit between the fork-point and
+is compared against each commit between the fork-point and .
+
+Every commit with a changeset that doesn't exist in the other branch
+has its id (sha1) reported, prefixed by a symbol. Those existing only
+in the branch are prefixed with a minus (-) sign, and those
+that only exist in the branch are prefixed with a plus (+) symbol.
+
+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 under a different commit id. For example,
+this will happen if you're feeding patches via email rather
+than pushing or pulling commits directly.
+
OPTIONS
-------