# fatal: git write-tree failed to write a tree 6 messages from 2009-02-28 to 2009-03-03. Participants: Caleb Cushing, Johannes Schindelin. Thread: https://gitlist.dev/t/18064 ## Caleb Cushing, 2009-02-28 16:25 Subject: fatal: git write-tree failed to write a tree Message-ID: <81bfc67a0902280825t507e385bvd25c846add2a299c@mail.gmail.com> URL: https://gitlist.dev/e/81bfc67a0902280825t507e385bvd25c846add2a299c%40mail.gmail.com ``` git merge java-overlay/master Adding profiles/package.mask/gentoo.org Adding profiles/package.mask/perl-experimental Adding profiles/package.mask/regen2.org Adding profiles/package.mask/sunrise profiles/package.mask/java-overlay: unmerged (f67eeb638e2593b2bee5c9b476e3044a8404916a) fatal: git write-tree failed to write a tree normally merges work fine... hmm... -- Caleb Cushing http://xenoterracide.blogspot.com ``` ## Johannes Schindelin, 2009-03-01 21:10 Subject: Re: fatal: git write-tree failed to write a tree Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.0903012210230.10279%40pacific.mpi-cbg.de In-Reply-To: <81bfc67a0902280825t507e385bvd25c846add2a299c@mail.gmail.com> ``` Hi, On Sat, 28 Feb 2009, Caleb Cushing wrote: > profiles/package.mask/java-overlay: unmerged > (f67eeb638e2593b2bee5c9b476e3044a8404916a) > fatal: git write-tree failed to write a tree A tree cannot contain unmerged files. Ciao, Dscho ``` ## Caleb Cushing, 2009-03-02 00:23 Subject: Re: fatal: git write-tree failed to write a tree Message-ID: <81bfc67a0903011623qc1f47fas57c3c8cea2a47eba@mail.gmail.com> URL: https://gitlist.dev/e/81bfc67a0903011623qc1f47fas57c3c8cea2a47eba%40mail.gmail.com In-Reply-To: ``` On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin wrote: > A tree cannot contain unmerged files. > I didn't do that, git did. I've tried running git reset --hard HEAD (and git status shows a clean tree before hand). so how can I resolve it? -- Caleb Cushing http://xenoterracide.blogspot.com ``` ## Caleb Cushing, 2009-03-03 05:47 Subject: Re: fatal: git write-tree failed to write a tree Message-ID: <81bfc67a0903022147m42e8fe38gb93773084614d30@mail.gmail.com> URL: https://gitlist.dev/e/81bfc67a0903022147m42e8fe38gb93773084614d30%40mail.gmail.com In-Reply-To: ``` On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin wrote: > A tree cannot contain unmerged files. so... still looking for a solution since it seems I can no longer do a merge from this remote. There has to be a way to get the tree back into a proper state... -- Caleb Cushing http://xenoterracide.blogspot.com ``` ## Johannes Schindelin, 2009-03-03 10:05 Subject: Re: fatal: git write-tree failed to write a tree Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.0903031103580.6399%40intel-tinevez-2-302 In-Reply-To: <81bfc67a0903022147m42e8fe38gb93773084614d30@mail.gmail.com> ``` Hi, On Tue, 3 Mar 2009, Caleb Cushing wrote: > On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin > wrote: > > A tree cannot contain unmerged files. > > > so... still looking for a solution since it seems I can no longer do a > merge from this remote. There has to be a way to get the tree back > into a proper state... You have a tree with unmerged entries. Why don't you look into the issue and solve it? A simple "git status" should show you what are the unmerged entries. A simple look at those files should show you conflict markers. Resolve the issue, commit, continue. Ciao, Dscho ``` ## Caleb Cushing, 2009-03-03 17:18 Subject: Re: fatal: git write-tree failed to write a tree Message-ID: <81bfc67a0903030918w3ccc88fcudfa8a2986e8e2415@mail.gmail.com> URL: https://gitlist.dev/e/81bfc67a0903030918w3ccc88fcudfa8a2986e8e2415%40mail.gmail.com In-Reply-To: ``` > > You have a tree with unmerged entries.  Why don't you look into the issue > and solve it?  A simple "git status" should show you what are the unmerged > entries.  A simple look at those files should show you conflict markers. > > Resolve the issue, commit, continue. no... not so simple... git mergetool comes back with (c)reated (d)eleted files. I want the created one. when I choose that and commit, no merge is capable of happening. it says (for that file) that there is nothing to change, in fact if nothing else has changed the branch will simply say nothing to commit once I've resolved it. all commits at this point are simply commits. -- Caleb Cushing http://xenoterracide.blogspot.com ```