1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "GIT-CHERRY-PICK" 1 "" "" ""
22 git-cherry-pick \- Apply the change introduced by an existing commit
26 \fIgit\-cherry\-pick\fR [\-\-edit] [\-n] [\-r] <commit>
31 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)\&.
37 Commit to cherry\-pick\&.
41 With this option, git\-cherry\-pick will let you edit the commit message prior committing\&.
45 Usually the command appends which commit was cherry\-picked after the original commit message when making a commit\&. This option, \fI\-\-replay\fR, causes it to use the original commit message intact\&. This is useful when you are reordering the patches in your private tree before publishing\&.
49 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\&.
51 This is useful when cherry\-picking more than one commits' effect to your working tree in a row\&.
56 Written by Junio C Hamano <junkio@cox\&.net>
61 Documentation by Junio C Hamano and the git\-list <git@vger\&.kernel\&.org>\&.
66 Part of the \fBgit\fR(7) suite