Hi,
On Wed, 11 Feb 2009, Mike Ralphson wrote:
quoted
On Tue, 10 Feb 2009, newren@gmail.com wrote:
fast-export will only list as parents those commits which have already
been traversed (making it appear as if merges have been squashed if not
all parents have been traversed). To avoid this silent squashing of
merge commits, we request commits in topological order.
Any comparative timings? We don't need to rename this to 'git
reasonably-speedy-export'? 8-)
What we _could_ do is add proper error handling: fast-export should
recognize that it did not see the commit yet, and error out suggesting
using --topo-order with fast-export.
Ciao,
Dscho