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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 27, 2010, 19:46 UTC
Message-ID
<7viq54fed7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1277646745.13370.711.camel@zarniwoop.blob>
Robert Spanton <rspanton@zepler.net> writes:
Show 5 quoted lines
> 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.

Previous: Robert Spanton
Message 2 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.