On Mon, Feb 9, 2009 at 4:17 AM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Sun, 8 Feb 2009, Elijah Newren wrote: > >> 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. Okay, I'll work on it. Sadly, making a branch based on commit E and trying to run using <E> instead of "--all" didn't reproduce the bug, so it must require some additional things to trigger this issue. I think I triggered the same issue on a closely related cvs2git-created repository that's only about 350M, so at least I have something smaller to work with. It may take me a while, but I'll report back when I've found more. Elijah -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
