GIT−CHERRY - Online Linux Manual PageSection : 1
Updated : 2023−03−13
Source : Git 2.40.0
Note : Git Manual
NAMEgit-cherry − Find commits yet to be applied to upstream
SYNOPSISgit cherry [−v] [<upstream> [<head> [<limit>]]]
DESCRIPTIONDetermine whether there are commits in <head>..<upstream> that are equivalent to those in the range <limit>..<head>. 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 git-cherry-pick(1), git-am(1) or git-rebase(1). 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.
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.
EXAMPLES
Patch workflowsgit−cherry is frequently used in patch−based workflows (see gitworkflows(7)) 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: $ 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 −v
Concrete 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
− cccc000... commit C
+ bbbb000... commit B
− aaaa000... commit AHere, we see that the commits A and C (marked with −) can be dropped from your topic branch when you rebase it on top of origin/master, while the commit B (marked with +) still needs to be kept so that it will be sent to be applied to origin/master.
Using a limitThe optional <limit> is useful in cases where your topic is based on other work that is not in upstream. Expanding on the previous example, this 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
| * 0000fff (base) unpublished stuff F
[... snip ...]
| * 0000aaa unpublished stuff A
|/
o 1234567 merge−base between upstream and topicBy specifying base as the limit, you can avoid listing commits between base and topic: $ git cherry origin/master topic base
− cccc000... commit C
+ bbbb000... commit B
− aaaa000... commit A
SEE ALSOgit-patch-id(1)
GITPart of the git(1) suite 0
Johanes Gumabo
Data Size : 12,871 byte
man-git-cherry.1Build : 2024-12-05, 20:55 :
Visitor Screen : x
Visitor Counter ( page / site ) : 3 / 200,905
Visitor ID : :
Visitor IP : 13.59.58.68 :
Visitor Provider : AMAZON-02 :
Provider Position ( lat x lon ) : 39.962500 x -83.006100 : x
Provider Accuracy Radius ( km ) : 1000 :
Provider City : Columbus :
Provider Province : Ohio , : ,
Provider Country : United States :
Provider Continent : North America :
Visitor Recorder : Version :
Visitor Recorder : Library :
Online Linux Manual Page : Version : Online Linux Manual Page - Fedora.40 - march=x86-64 - mtune=generic - 24.12.05
Online Linux Manual Page : Library : lib_c - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Online Linux Manual Page : Library : lib_m - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Data Base : Version : Online Linux Manual Page Database - 24.04.13 - march=x86-64 - mtune=generic - fedora-38
Data Base : Library : lib_c - 23.02.07 - march=x86-64 - mtune=generic - fedora.36
Very long time ago, I have the best tutor, Wenzel Svojanovsky . If someone knows the email address of Wenzel Svojanovsky , please send an email to johanes_gumabo@yahoo.co.id .
If error, please print screen and send to johanes_gumabo@yahoo.co.id
Under development. Support me via PayPal.