git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
RSRobert Spanton <rspanton@zepler.net>
Date
Jun 27, 2010, 13:52 UTC
Message-ID
<1277646745.13370.711.camel@zarniwoop.blob>

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
Next: Junio C Hamano
Message 1 of 2 in “Clarify that git-cherry-pick applies patches to HEAD”
  1. Clarify that git-cherry-pick applies patches to HEADRobert Spanton, Jun 27, 2010
  2. Junio C HamanoJun 27, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.