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

Re: how to most effectively cherry pick by selective patch hunk?

From
Jeff King <peff@peff.net>
Date
Feb 9, 2021, 16:39 UTC
Message-ID
<YCK6w/VbfUtM68Ad@coredump.intra.peff.net>
In-Reply-To
<566b38df-307c-f342-b583-3a50a81b5057@crashcourse.ca>
On Tue, Feb 09, 2021 at 08:58:06AM -0500, Robert P. J. Day wrote:
>   what would be great is some sort of "-p" (patch selection) option
> with cherry-pick, but i don't see that.

We have "checkout -p", but of course the problem there is that it's picking out of the whole state of that commit. So you might see other changes not introduced by that commit.

Conceptually, adding "cherry-pick -p" would be pretty easy. The strategy for all of the "-p" options is to generate a diff, then feed that diff to the patch-selection code, then apply whatever the user selects. For "checkout -p $commit", that diff is the diff between $commit and our current state. But for "cherry-pick -p", it would be the diff between $commit^ and $commit.

Of course that involves a change to Git, and you were looking for something you could do with existing versions. :) You can emulate it by making the commit's parent equivalent to your current state. I.e.:

  git checkout --detach ;# detached HEAD for temporary commit
  git cherry-pick $commit ;# maybe deal with conflicts
  commit=$(git rev-parse --verify HEAD) ;# remember the temp commit
  git checkout - ;# back to your branch
  git checkout -p $commit
-Peff
Previous: Robert P. J. DayNext: Robert P. J. Day
Message 2 of 5 in “how to most effectively cherry pick by selective patch hunk?”
  1. Robert P. J. DayFeb 9, 2021
  2. Jeff KingFeb 9, 2021
  3. Robert P. J. DayFeb 9, 2021
  4. Andreas SchwabFeb 9, 2021
  5. Elijah NewrenFeb 11, 2021

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.