projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2e987f9) | patch
gitweb.js: No need for inProgress in blame_incremental.js
authorJakub Narebski <jnareb@gmail.com>
Fri, 27 May 2011 13:49:59 +0000 (15:49 +0200)
committerJunio C Hamano <gitster@pobox.com>
Fri, 27 May 2011 18:00:35 +0000 (11:00 -0700)
commit4510165934eba7be94dea822e2fb1cfa89e70ca3
tree22edea642169da904ef7435ad3a0ad11afdd8debtree | snapshot
parent2e987f92408f5ddd20246d7d9553b57d90767d54commit | diff
gitweb.js: No need for inProgress in blame_incremental.js

JavaScript is single-threaded, so there is no need for protection
against re-entrancy via inProgress variable.

In particular calls to setInterval handler are stacked if handler
doesn't finish before new interrupt (before new interval).  The same
happens with events - they are (hopefully) stacked if even handler
didn't finish work.

Signed-off-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
gitweb/static/js/blame_incremental.js diff | blob | history
Git—the stupid content tracker