Junio C Hamano <gitster@xxxxxxxxx> wrote: > * Incremental blame > > It does not seem to break the blame, but at least from where I > sit accessing repo.or.cz this does not look incremental to me. > The entire browser session freezes until the blame page > displays in full. My local installation behaves the same way. What kind of repo are you trying that on? I haven't myself tried the gitweb incremental blame but I do know that one of my day-job repositories can take *ages* for git-gui's `git blame --incremental -C -C -w` pass. Most of the revisions for some of the blobs are far back in history, and there's a lot of files to look at for copy/movement. Plus some of that history is downright *messy* (I posted gitk screenshots of it not too long ago). I'll try to give the gitweb incremental blame a try on that repo tomorrow. -- Shawn. - 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
