X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=Documentation%2Fgit-cherry-pick.txt;h=bfa950ca19c701bd3837a874bbeeb18b440ed44f;hb=2f57c69792146e6c178a05edec18ab15d0138ad6;hp=e6a8c878538acd32061546dac365634cdd532a89;hpb=0493a3fd5204a36bc961a8611770ddb9ec1ed8ed;p=git.git diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt index e6a8c878..bfa950ca 100644 --- a/Documentation/git-cherry-pick.txt +++ b/Documentation/git-cherry-pick.txt @@ -1,14 +1,13 @@ git-cherry-pick(1) ================== -v0.99.5 Aug 2005 NAME ---- -git-cherry-pick - Apply the change introduced by an existing commit. +git-cherry-pick - Apply the change introduced by an existing commit SYNOPSIS -------- -'git-cherry-pick' [-n] [-r] +'git-cherry-pick' [--edit] [-n] [-r] DESCRIPTION ----------- @@ -21,15 +20,19 @@ OPTIONS :: Commit to cherry-pick. --r:: - Usuall the command appends which commit was +-e|--edit:: + With this option, `git-cherry-pick` will let you edit the commit + message prior committing. + +-r|--replay:: + Usually 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'. + before publishing. --n:: +-n|--no-commit:: Usually the command automatically creates a commit with a commit log message stating which commit was cherry-picked. This flag applies the change necessary @@ -38,9 +41,9 @@ OPTIONS 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. ++ +This is useful when cherry-picking more than one commits' +effect to your working tree in a row. Author