blob: 875edb6b9f5ddc6d19b2de29cebbad5ebb7d37a0 [file] [log] [blame]
git-cherry-pick - Apply the change introduced by an existing commit
'git-cherry-pick' [--edit] [-n] [-x] <commit>
Given one existing commit, apply the change the patch introduces, and record a
new commit that records it. This requires your working tree to be clean (no
modifications from the HEAD commit).
Commit to cherry-pick.
With this option, `git-cherry-pick` will let you edit the commit
message prior committing.
Cause the command to append which commit was
cherry-picked after the original commit message when
making a commit. Do not use this option if you are
cherry-picking from your private branch because the
information is useless to the recipient. If on the
other hand you are cherry-picking between two publicly
visible branches (e.g. backporting a fix to a
maintenance branch for an older release from a
development branch), adding this information can be
It used to be that the command defaulted to do `-x`
described above, and `-r` was to disable it. Now the
default is not to do `-x` so this option is a no-op.
Usually the command automatically creates a commit with
a commit log message stating which commit was
cherry-picked. This flag applies the change necessary
to cherry-pick the named commit to your working tree,
but does not make the commit. In addition, when this
option is used, your working tree does not have to match
the HEAD commit. The cherry-pick is done against the
beginning state of your working tree.
This is useful when cherry-picking more than one commits'
effect to your working tree in a row.
Written by Junio C Hamano <>
Documentation by Junio C Hamano and the git-list <>.
Part of the gitlink:git[7] suite