git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/3] gitweb: Improving blame_incremental.js

From
Jakub Narebski <jnareb@gmail.com>
Date
May 27, 2011, 14:04 UTC
Message-ID
<201105271604.41731.jnareb@gmail.com>
In-Reply-To
<1306504201-18014-1-git-send-email-jnareb@gmail.com>
Jakub Narebski wrote:
Show 12 quoted lines
> Two first patches remove unnecessary code from JavaScript-side of
> blame_incremental code. [...]
> 
> So those two are pure simplification.
> 
> 
> The third (last) patch replaces setInterval (where events might
> accumulate if browser is very busy) to recommended re-enabled
> setTimeout.  [...]
> 
> This one adds more code than it removes, and could be split into two
> patches: [...]

I forgot to add that this series is based on top of jn/gitweb-js series, namely it theoretically require "gitweb: Split JavaScript for maintability, combining on build"... but thanks to Git rename detection it should [had] apply on top of master as well.

-- 
Jakub Narebski
Poland
Previous: Jakub Narebski
Message 5 of 5 in “gitweb: Improving blame_incremental.js”
  1. 0/3 gitweb: Improving blame_incremental.jsJakub Narebski, May 27, 2011
  2. 1/3 gitweb.js: No need for inProgress in blame_incremental.jsJakub Narebski, May 27, 2011
  3. 2/3 gitweb.js: No need for loop in blame_incremental's handleResponse()Jakub Narebski, May 27, 2011
  4. 3/3 gitweb.js: use setTimeout rather than setInterval in blame_incremental.jsJakub Narebski, May 27, 2011
  5. Jakub NarebskiMay 27, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.