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
Robert P. J. Day <rpjday@crashcourse.ca>
Date
Feb 9, 2021, 16:58 UTC
Message-ID
<4fe5247a-96d6-c4a-97f8-9ede175adf90@crashcourse.ca>
In-Reply-To
<YCK6w/VbfUtM68Ad@coredump.intra.peff.net>
On Tue, 9 Feb 2021, Jeff King wrote:
Show 8 quoted lines
> 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.
  this is probably what i'll use since i can use <pathspec> to grab
only the patch file from that commit, then add and commit it manually
from there.
rday
Previous: Jeff KingNext: Andreas Schwab
Message 3 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.