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

Re: What's cooking in git.git (Sep 2009, #02; Mon, 07)

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 8, 2009, 13:10 UTC
Message-ID
<m3k509vaym.fsf@localhost.localdomain>
In-Reply-To
<7vtyzexnhm.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * jn/gitweb-show-size (2009-09-07) 1 commit
>  - gitweb: Add 'show-sizes' feature to show blob sizes in tree view
This is an RFC, because of a) feature naming, and b) tests.
It does work correctly, though.
 
> * jn/gitweb-blame (2009-09-01) 5 commits
>  - gitweb: Minify gitweb.js if JSMIN is defined
>  - gitweb: Create links leading to 'blame_incremental' using JavaScript
>   (merged to 'next' on 2009-09-07 at 3622199)

I plan on reverting the order of those two patches, as JSMIN patch is more ready than 'blame_incremental' linking.

With JSMIN there is perhaps question of documenting it, and whether git-instaweb.sh should use minified JavaScript or not (curently it does not). With 'blame_incremental' linking there are quite a few issues:

 1. When to do JavaScript detection
    a. on load (current solution)
    b. on click (via event handler)
 2. How to invoke actions requiring JavaScript
    a. add 'js=1' parameter (perhaps limiting URLs, as not to
       add it e.g. to http://git-scm.com/ $home_link)
    b. rewrite action parameter, e.g. from 'blame' to
       'blame_incremental' (troubles with path_info URLs)
    c. use cookies
Current solution works, but I think is suboptimal.
Show 5 quoted lines
>  + gitweb: Colorize 'blame_incremental' view during processing
>  + gitweb: Incremental blame (using JavaScript)
>  + gitweb: Add optional "time to generate page" info in footer
> 
> Ajax-y blame.

I'd very much like for others to check if it works with other browsers (Internet Explorer 6, 7, 8; Opera 9, 10; Safari; Firefox 2, 3, 3.5)

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Junio C HamanoNext: Sverre Rabbelier
Message 4 of 24 in “What's cooking in git.git (Sep 2009, #02; Mon, 07)”
  1. Junio C HamanoSep 8, 2009
  2. Nanako ShiraishiSep 8, 2009
  3. Junio C HamanoSep 8, 2009
  4. Jakub NarebskiSep 8, 2009
  5. Sverre RabbelierSep 8, 2009
  6. jk/1.7.0-status, was: What's cooking in git.git (Sep 2009, #02; Mon, 07)Jeff King, Sep 9, 2009
  7. Daniel BarkalowSep 10, 2009
  8. Johannes SchindelinSep 10, 2009
  9. Daniel BarkalowSep 10, 2009
  10. Junio C HamanoSep 10, 2009
  11. scissors definition and documentationNicolas Sebrecht, Sep 11, 2009
  12. 1/2 mailinfo: add '--scissors' to usage messageNicolas Sebrecht, Sep 11, 2009
  13. 2/2 add documentation for mailinfo.scissors and '--no-scissors'Nicolas Sebrecht, Sep 11, 2009
  14. add documentation for mailinfo.scissors and '--no-scissors'Nicolas Sebrecht, Sep 11, 2009
  15. Junio C HamanoSep 11, 2009
  16. Re: add documentation for mailinfo.scissors and '--no-scissors'Nicolas Sebrecht, Sep 11, 2009
  17. Junio C HamanoSep 11, 2009
  18. Re: add documentation for mailinfo.scissors and '--no-scissors'Nicolas Sebrecht, Sep 11, 2009
  19. Junio C HamanoSep 11, 2009
  20. Re: add documentation for mailinfo.scissors and '--no-scissors'Nicolas Sebrecht, Sep 12, 2009
  21. 2/2 add documentation for mailinfo.scissors and '--no-scissors'Nicolas Sebrecht, Sep 11, 2009
  22. Junio C HamanoSep 12, 2009
  23. Junio C HamanoSep 12, 2009
  24. Sverre RabbelierSep 12, 2009

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.