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

Re: Error in git-cherry-pick manpage?

From
PHPete Harlan <pgit@pcharlan.com>
Date
Nov 18, 2008, 19:34 UTC
Message-ID
<492318AF.8080004@pcharlan.com>
In-Reply-To
<20081114151426.GA20985@merkur.sol.de>
Jens Seidel wrote:
Show 19 quoted lines
> Hi,
> 
> I try to use git cherry-pick to combine multiple commits but I'm confused
> about the second sentence of the description:
> 
> "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)."
> 
> I intent to use it as follows:
> 
>  git cherry-pick -x --no-commit 2e855ae
>  git cherry-pick -x --no-commit 0c1151
>  ...
> 
> After the first invocation my working tree will not be clean but contain
> changes in the index.
> 
> Does this mean that's a wrong usage of cherry-pick?
If it is, you might try this:
  git cherry-pick -x 2e855ae             # Let it commit
  git cherry-pick -x --no-commit 0c1151  # Will stage changes
  git commit --amend
  # Repeat last two steps as needed...
--Pete
Previous: Jens Seidel
Message 2 of 2 in “Error in git-cherry-pick manpage?”
  1. Jens SeidelNov 14, 2008
  2. Pete HarlanNov 18, 2008

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.