Quantcast

fatal: git write-tree failed to write a tree

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

fatal: git write-tree failed to write a tree

Caleb Cushing
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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fatal: git write-tree failed to write a tree

Johannes Schindelin
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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fatal: git write-tree failed to write a tree

Caleb Cushing
On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin
<[hidden email]> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fatal: git write-tree failed to write a tree

Caleb Cushing
In reply to this post by Johannes Schindelin
On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin
<[hidden email]> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fatal: git write-tree failed to write a tree

Johannes Schindelin
Hi,

On Tue, 3 Mar 2009, Caleb Cushing wrote:

> On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin
> <[hidden email]> 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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fatal: git write-tree failed to write a tree

Caleb Cushing
>
> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Loading...