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

Re: No way to resolve git am conflicts.

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 8, 2011, 16:36 UTC
Message-ID
<20110108163633.GB28898@burratino>
In-Reply-To
<ig9nqq$4ib$1@dough.gmane.org>
Stephen Kelly wrote:
> git am the.patch
[...]
Show 10 quoted lines
> Applying: Introduce new configuation option to override committer 
> information
> error: patch failed: builtin/commit.c:1352
> error: builtin/commit.c: patch does not apply
> Patch failed at 0001 Introduce new configuation option to override committer 
> information
> When you have resolved this problem run "git am --resolved".
> If you would prefer to skip this patch, instead run "git am --skip".
> To restore the original branch and stop patching run "git am --abort".
> $ git diff
[...]
> As git status doesn't tell me what the conflict is, I can't resolve it.

Have you tried "git am -3" or "git am --reject" (after "git am --abort")?

I agree that the hints printed are suboptimal in this case. Please feel free to make them better if you have time for it. :)

Previous: Stephen KellyNext: Stephen Kelly
Message 2 of 3 in “No way to resolve git am conflicts.”
  1. Stephen KellyJan 8, 2011
  2. Jonathan NiederJan 8, 2011
  3. Stephen KellyJan 8, 2011

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.