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
Johannes Sixt <j6t@kdbg.org>
Date
Nov 7, 2025, 06:37 UTC
Message-ID
<e1fede83-bed0-49e9-84a0-f026b9df6039@kdbg.org>
In-Reply-To
<CAEyHQXWd77_jJachC6FYbWMJ+L=KkKoUqiACQ7z8r-ZwYq8JYw@mail.gmail.com>
Am 07.11.25 um 05:39 schrieb Bhavik Bavishi:
Show 12 quoted lines
> What did you do before the bug happened? (Steps to reproduce your issue)
>> ran git cherry-pick command, which went fine without any error, but missed to apply change
>> created patch with 'git fromat-patch' and applied with 'git apply --verbose', which error for the issue
> 
> What did you expect to happen? (Expected behavior)
>> git cherry-pick should fail, since it failed to apply hunk
> 
> What happened instead? (Actual behavior)
>> git cherry-pick completed successfully without any error
> 
> What's different between what you expected and what actually happened?
>> git apply --verbose, failed with error about the issue, whereas git cherry-pick didn't fail for the same

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?

-- Hannes
Previous: Bhavik BavishiNext: Bhavik Bavishi
Message 2 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.