* fatal: git write-tree failed to write a tree
@ 2009-02-28 16:25 Caleb Cushing
2009-03-01 21:10 ` Johannes Schindelin
0 siblings, 1 reply; 6+ messages in thread
From: Caleb Cushing @ 2009-02-28 16:25 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: fatal: git write-tree failed to write a tree
2009-02-28 16:25 fatal: git write-tree failed to write a tree Caleb Cushing
@ 2009-03-01 21:10 ` Johannes Schindelin
2009-03-02 0:23 ` Caleb Cushing
2009-03-03 5:47 ` Caleb Cushing
0 siblings, 2 replies; 6+ messages in thread
From: Johannes Schindelin @ 2009-03-01 21:10 UTC (permalink / raw)
To: Caleb Cushing; +Cc: git
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: fatal: git write-tree failed to write a tree
2009-03-01 21:10 ` Johannes Schindelin
@ 2009-03-02 0:23 ` Caleb Cushing
2009-03-03 5:47 ` Caleb Cushing
1 sibling, 0 replies; 6+ messages in thread
From: Caleb Cushing @ 2009-03-02 0:23 UTC (permalink / raw)
To: Johannes Schindelin; +Cc: git
On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: fatal: git write-tree failed to write a tree
2009-03-01 21:10 ` Johannes Schindelin
2009-03-02 0:23 ` Caleb Cushing
@ 2009-03-03 5:47 ` Caleb Cushing
2009-03-03 10:05 ` Johannes Schindelin
1 sibling, 1 reply; 6+ messages in thread
From: Caleb Cushing @ 2009-03-03 5:47 UTC (permalink / raw)
To: Johannes Schindelin; +Cc: git
On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: fatal: git write-tree failed to write a tree
2009-03-03 5:47 ` Caleb Cushing
@ 2009-03-03 10:05 ` Johannes Schindelin
2009-03-03 17:18 ` Caleb Cushing
0 siblings, 1 reply; 6+ messages in thread
From: Johannes Schindelin @ 2009-03-03 10:05 UTC (permalink / raw)
To: Caleb Cushing; +Cc: git
Hi,
On Tue, 3 Mar 2009, Caleb Cushing wrote:
> On Sun, Mar 1, 2009 at 4:10 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: fatal: git write-tree failed to write a tree
2009-03-03 10:05 ` Johannes Schindelin
@ 2009-03-03 17:18 ` Caleb Cushing
0 siblings, 0 replies; 6+ messages in thread
From: Caleb Cushing @ 2009-03-03 17:18 UTC (permalink / raw)
To: Johannes Schindelin; +Cc: git
>
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-03-03 17:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-28 16:25 fatal: git write-tree failed to write a tree Caleb Cushing
2009-03-01 21:10 ` Johannes Schindelin
2009-03-02 0:23 ` Caleb Cushing
2009-03-03 5:47 ` Caleb Cushing
2009-03-03 10:05 ` Johannes Schindelin
2009-03-03 17:18 ` Caleb Cushing
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).