Jakub Narebski <jnareb@xxxxxxxxx> writes: > But even if incremental blame turns out to be slower than incremental > blame it still has the advantage of being _incremental_. You have at > least some result soon. It wasn't it was slow that bothered me, but early implementations of incremental blame I tried didn't _appear_ as incremental. That was the dissapointing part. At the protocol and implementation level it certainly was feeding data incrementally to the browser, but the end user experience on the screen was "click....wait...wait...wait...voila the whole blame appears", not "click...trickle...trickle...trickle...ah everything is filled". The latter obviously is what an incremental one should be aiming for. No I haven't tried your latest code. Probably I should. -- 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