Re: git-fast-export bug, commits emmitted in incorrect order causing parent data to be lost from commits turning essentially linear repo into "islands"

From: Yves Orton <yves.orton@booking.com>
Date: Jun 12, 2008, 12:04 UTC
Message-ID: <1213272285.6940.222.camel@gemini>
In-Reply-To: <48510E2E.6090508@viscovery.net>

On Thu, 2008-06-12 at 13:53 +0200, Johannes Sixt wrote:

Show 13 quoted lines

> Yves Orton schrieb:
> > Hi,
> > 
> > Ive been working with git-fast-export a bit recently and Ive hit a bug
> > that is causing some trouble. 
> > 
> > Essentially it seems that one of our repos git-fast-export fails to emit
> > the proper 'from' information for several commits in the repo. These
> > commits are emitted first without parent data even though their parents
> > ARE emitted later.
> 
> Does it make a difference if you pass --topo-order to git fast-export?
> (But I don't know for certain that this is even legal.)

Yes it does make a difference. A big difference. That would be the workaround I really needed. At least currently thats the way it looks, i havent thoroughly tested the result yet but it certainly looks right.

Perhaps this should be enabled by default to avoid the problem i encountered? At least until whatever the cause of the root problem is identified and fixed.

Thanks a lot. ++ to you.

Cheers, yves