[PATCH] Clarify that git-cherry-pick applies patches to HEAD

[PATCH] Clarify that git-cherry-pick applies patches to HEAD

[Robert Spanton]

Change the description of cherry-pick to state that the given commits
are applied to the current HEAD.  It was unclear exactly where
cherry-pick ends up sticking the given commits.

Signed-off-by: Robert Spanton <rspanton@zepler.net>
---
 Documentation/git-cherry-pick.txt |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
index bcb4c75..2d52445 100644
--- a/Documentation/git-cherry-pick.txt
+++ b/Documentation/git-cherry-pick.txt
@@ -13,8 +13,9 @@ DESCRIPTION
 -----------
 
 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).
+introduces to the current HEAD, recording a new commit for each.
+This requires your working tree to be clean (no modifications from
+the HEAD commit).
 
 OPTIONS
 -------
-- 
1.7.0.1

Re: [PATCH] Clarify that git-cherry-pick applies patches to HEAD

[Junio C Hamano]

Robert Spanton <rspanton@zepler.net> writes:

> Change the description of cherry-pick to state that the given commits
> are applied to the current HEAD.  It was unclear exactly where
> cherry-pick ends up sticking the given commits.
>
> Signed-off-by: Robert Spanton <rspanton@zepler.net>

Almost all commit-creating commands work on nothing but the current HEAD,
and once a reader understands that repeating that "git commit" makes
commit on top of current HEAD, "git am" applies patches on top of current
HEAD, etc. will become excessively noisy, I am afraid.