Re: identical hashes on two branches, but holes in git log

Philippe De Muyter [off-list ref] writes:

So we trade correctness for speed :(

No corretness is traded with anything else here.

There are applications where topology matters and where it doesn't.
When topology really matters (e.g. drawing the graph), the caller
can choose to use --topo-order to have git do the work.  Of course
the caller could accept output without --topo-order in streaming
fashion and stitch the parent-child relationship itself.

And of course, in applications where topology does not matter, you
do not have to wait.

That is called "choice", not "trading".