Questions tagged [git-cherry-pick]

This command applies the changes introduced by some existing commits.

Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit).

When it is not obvious how to apply a change, the following happens:

  • The current branch and HEAD pointer stay at the last commit successfully made.

  • The CHERRY_PICK_HEAD ref is set to point at the commit that introduced the change that is difficult to apply.

  • Paths in which the change applied cleanly are updated both in the index file and in your working tree.

  • For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of git-merge(1). The working tree files will include a description of the conflict bracketed by the usual conflict markers <<<<<<< and >>>>>>>.

  • No other modifications are made.

See git-merge for some hints on resolving such conflicts.

Links

376 questions
-6
votes
1 answer

Who can help me in fixing the cherry-pick Git error?

fiqri@fiqri-X441UA:~/android_kernel_xiaomi_vince-4.9$ git cherry-pick 89a3491a2092de1d672644b273fcdfea46604319 error: commit 89a3491a2092de1d672644b273fcdfea46604319 is a merge but no -m option was given. fatal: cherry-pick failed
1 2 3
25
26