| commit | 4510165934eba7be94dea822e2fb1cfa89e70ca3 | |
| author | Jakub Narebski <jnareb@gmail.com> | |
| Fri, 27 May 2011 13:49:59 +0000 (27 15:49 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 27 May 2011 18:00:35 +0000 (27 11:00 -0700) | ||
| tree | 22edea642169da904ef7435ad3a0ad11afdd8deb | treesnapshot (tar.gz zip) |
| parent | 2e987f92408f5ddd20246d7d9553b57d90767d54 | commitdiff |
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>
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 | diffblobblamehistory |