Linux "git-cherry" Command Line Options and Examples
Find commits yet to be applied to upstream
Determine whether there are commits in <head>..<upstream> that are equivalent to those in the range <limit>.
Usage:
git cherry [-v] [
Command Line Options:
-v
Show the commit subjects next to the SHA1s.<upstream>Upstream branch to search for equivalent commits. Defaults to the upstream branch of HEAD.<head>Working branch; defaults to HEAD.<limit>Do not report commits up to (and including) limit.EXAMPLESPatch workflowsgit-cherry is frequently used in patch-based workflows (see gitworkflows(7)) to determine if a series of patches has been applied bythe upstream maintainer. In such a workflow you might create and send a topic branch like this:$ git checkout -b topic origin/master# work and create some commits$ git format-patch origin/master$ git send-email ... 00*Later, you can see whether your changes have been applied by saying (still on topic):$ git fetch # update your notion of origin/master$ git cherry -vConcrete exampleIn a situation where topic consisted of three commits, and the maintainer applied two of them, the situation might look like:$ git log --graph --oneline --decorate --boundary origin/master...topic* 7654321 (origin/master) upstream tip commit[... snip some other commits ...]* cccc111 cherry-pick of C* aaaa111 cherry-pick of A[... snip a lot more that has happened ...]| * cccc000 (topic) commit C| * bbbb000 commit B| * aaaa000 commit A|/o 1234567 branch pointIn such cases, git-cherry shows a concise summary of what has yet to be applied:$ git cherry origin/master topic
git-cherry -v ...
-
+ bbbb000... commit B
git-cherry - ...