path: root/Documentation/git-cherry-pick.txt
diff options
Diffstat (limited to 'Documentation/git-cherry-pick.txt')
1 files changed, 57 insertions, 0 deletions
diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
new file mode 100644
index 0000000..38a4875
--- /dev/null
+++ b/Documentation/git-cherry-pick.txt
@@ -0,0 +1,57 @@
+v0.99.5 Aug 2005
+git-cherry-pick - Apply the change introduced by an existing commit.
+'git-cherry-pick' [-n] [-r] <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.
+ Usuall the command appends which commit was
+ cherry-picked after the original commit message when
+ making a commit. This option, '--replay', causes it to
+ use the original commit message intact. This is useful
+ when you are reordering the patches in your private tree
+ before publishing, and is used by 'git rebase'.
+ 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 link:git.html[git] suite