| commit | e8dd0e4063da6d0eecef1a6db99534e41f74b32e | |
| author | Jakub Narebski <jnareb@gmail.com> | |
| Fri, 27 May 2011 13:50:00 +0000 (27 15:50 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 27 May 2011 18:00:39 +0000 (27 11:00 -0700) | ||
| tree | fa8cfddfcc0c34d0b3787b83f8de08aa4e5de5ac | treesnapshot (tar.gz zip) |
| parent | 4510165934eba7be94dea822e2fb1cfa89e70ca3 | commitdiff |
gitweb.js: No need for loop in blame_incremental's handleResponse()
JavaScript is single-threaded, so there is no need for protecting
against changes to XMLHttpRequest object behind event handler back.
Therefore there is no need for loop that was here in case `xhr' got
new changes while processing current changes. This should make code a
bit more clear.
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 protecting
against changes to XMLHttpRequest object behind event handler back.
Therefore there is no need for loop that was here in case `xhr' got
new changes while processing current changes. This should make code a
bit more clear.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| gitweb/static/js/blame_incremental.js | diffblobblamehistory |