git-cherry(1)'s "description" section has never really managed to
explain to me what the command does. It contains too much explanation
of the algorithm instead of simply saying what goals it achieves, and
too much terminology that we otherwise do not use (fork-point instead
Try a much more concise approach: state what it finds out, why this is
neat, and how the output is formatted, in a few short paragraphs. In
return, provide a longer example of how it fits into a format-patch/am
Also carefully avoid using "merge" in a context where it does not mean
something that comes from git-merge(1). Instead, say "apply" in an
attempt to further link to patch workflow concepts.
While there, also omit the language about _which_ upstream branch we
treat as the default. I literally just learned that we support having
several, so let's not confuse new users here, especially considering
that git-config(1) does _not_ document this.
Prompted-by: a.hue...@commend.com on #git
Signed-off-by: Thomas Rast <t...@thomasrast.ch>
Documentation/git-cherry.txt | 73 +++++++++++++++++++++++++-------------------
1 file changed, 41 insertions(+), 32 deletions(-)
diff --git a/Documentation/git-cherry.txt b/Documentation/git-cherry.txt
index 2d0daae..78ffddf 100644
@@ -3,7 +3,7 @@ git-cherry(1)
-git-cherry - Find commits not merged upstream
+git-cherry - Find commits not applied in upstream
@@ -12,46 +12,27 @@ SYNOPSIS
-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 diffs are compared after removing any whitespace and line numbers.
+Determine whether there are commits in `<head>..<upstream>` that are
+equivalent to those in the range `<limit>..<head>`.
-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.
+The equivalence test is based on the diff, after removing whitespace
+and line numbers. git-cherry therefore detects when commits have been
+"copied" by means of linkgit:git-cherry-pick, linkgit:git-am or
+Outputs the SHA1 of every commit in `<limit>..<head>`, prefixed with
+`-` for commits that have an equivalent in <upstream>, and `+` for
+commits that do not.
+ Verbose. Currently shows the commit subjects next to their
Upstream branch to compare against.
- Defaults to the first tracked remote branch, if available.
+ Defaults to the upstream branch of HEAD.
Working branch; defaults to HEAD.
@@ -59,6 +40,34 @@ OPTIONS
Do not report commits up to (and including) limit.
+git-cherry is frequently used in patch-based workflows (see
+linkgit:gitworkflows) to determine if a series of patches has been
+applied by the upstream maintainer. In such a workflow you might
+create and send a topic branch like this (fill in appropriate
+arguments for `...`):
+git checkout -b topic origin/master
+# work and create some commits
+git format-patch origin/master
+git send-email ... 00*
+Later, you can whether your changes have been applied by saying (still
+git fetch # update your notion of origin/master
+git cherry -v
+Note that this uses , and assumes that
+`core.autosetupmerge` is enabled (the default).
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html