Re: git fast-export issue -- anyone know if this is a bug or a feature?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 9, 2009, 11:17 UTC
Message-ID: <alpine.DEB.1.00.0902091216220.10279@pacific.mpi-cbg.de>
In-Reply-To: <51419b2c0902082131o512e966l1fb3029c7513b02e@mail.gmail.com>

Hi,

On Sun, 8 Feb 2009, Elijah Newren wrote:

Show 27 quoted lines

> In the source repository, I noticed that 6 of the earliest commits in 
> one root of history looked like:
> 
>      /--E
>     /  /
> A--C--D
>   /
>  B
> 
> In the "mirrored" repository, I notice this history had been modified
> so that it looked like
> 
>         E
>        /
> A--C--D
>   /
>  B
> 
> The latter history seems much more sane to me; since D is a child of
> C, making E a merge of C and D seemed really weird.  I did pour over
> the output of git fast-export --all to see if the merge directives
> were as expected, in order to see whether git fast-export or git
> fast-import were to be credited with the history fix.  It looks to me
> like git-fast-export reports no merge parents for E, so this seems to
> be on the fast-export side.
> 
> Is this, by chance, intentional?  (I'm using git-1.6.0.6, if it matters.)

Nope.

Please try to make a reproduction recipe (preferably as a patch to t9301); it seems that you are half-way there already.

Thanks, Dscho