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

Re: fatal: git-write-tree: not able to write tree

From
Junio C Hamano <junkio@cox.net>
Date
Apr 28, 2006, 08:32 UTC
Message-ID
<7vd5f2drr8.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200604280430.33100.len.brown@intel.com>
Len Brown <len.brown@intel.com> writes:
Show 17 quoted lines
> I'm trying to  use git-am to apply a patch series in a mailbox.
>
> The first patch has a conflict, which I edit to fix, and and then invoke
> git am --3way --interactive --signoff --utf8 --resolved
>
> but it bails out with this:
>
> drivers/acpi/thermal.c: unmerged (4829f067a3e7acfbeed8b230caac00b1ed4b8554)
> drivers/acpi/thermal.c: unmerged (528d198c28512af1627cce481575f37a599c0fe8)
> drivers/acpi/thermal.c: unmerged (db3bef1a3e51801128e7553f3e546c8272cc9ee1)
> fatal: git-write-tree: not able to write tree
>
> I've tried various incantations of git reset on the theory that there is some 
> old state hanging around someplace, but have not been able to check in this 
> file.
>
> clues?

Please say "--resolved" after you have actually resolved them, eh, meaning, (1) edit the working tree file into a desired shape, and (2) git-update-index drivers/acpi/thermal.c.

I've considered making --resolved to do update-index for all paths that are unmerged in the index, but that risks going forward by mistake when you still have other paths to resolve, so...

Previous: Len Brown
Message 2 of 2 in “fatal: git-write-tree: not able to write tree”
  1. Len BrownApr 28, 2006
  2. Junio C HamanoApr 28, 2006

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.