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

Re: [Bug report] git cherry-pick silently ignores error whereas git apply fails for hunk apply

From
Bhavik Bavishi <bhavikdbavishi@gmail.com>
Date
Nov 8, 2025, 03:44 UTC
Message-ID
<CAEyHQXUgzRnT=8Fydn9Ew6V29hfJcjR8i26mdvGOXaWD=agzNA@mail.gmail.com>
In-Reply-To
<CAEyHQXWd4kN=ehWh0Y7xNnPGk3ofXEc4=PvSYaZM91TFyLtnpg@mail.gmail.com>
> > If you use `git apply --3way`, does it still fail, or does it succeed
> > and does it produce the same result as `git cherry-pick` or a different
> > result?
> I've compare the file content of `mango/utils/apple_utils.cc` for `git
apply --3way` and  `git cherry-pick` is same

If I understand correctly, `git cherry-pick` is processed as expected, but for some reason we are not able to follow this behavior because the end result is missing content. expectation was to have this content either be applied successfully or fail with a conflict (indicating it could not be applied).

query: is there a way to understand this behavior? Based on that, we can then correct or update the file format to avoid such issues in the future, or introduce an additional process to run `git apply` (without `--3way`) and check if there is any hunk failed to apply and notify for the same.

Previous: Bhavik BavishiNext: Johannes Sixt
Message 4 of 7 in “[Bug report] git cherry-pick silently ignores error whereas git apply fails for hunk apply”
  1. Bhavik BavishiNov 7, 2025
  2. Johannes SixtNov 7, 2025
  3. Bhavik BavishiNov 7, 2025
  4. Bhavik BavishiNov 8, 2025
  5. Johannes SixtNov 8, 2025
  6. Chris TorekNov 8, 2025
  7. Bhavik BavishiNov 9, 2025

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.