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

Re: RFD: Shipping GitBrowser.js for instaweb

From
Jakub Narebski <jnareb@gmail.com>
Date
May 2, 2010, 20:14 UTC
Message-ID
<m3wrvmf4ei.fsf@localhost.localdomain>
In-Reply-To
<4BDDA780.7090500@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
Show 10 quoted lines
> I was wondering whether it would make sense to ship GitBrowser.js with
> Git and how much it would take to do so.
> 
> My personal answer to the 1st Q is Yes: instaweb as well as simple
> gitweb installs would benefit from a graphical DAG viewer.
> 
> About the required effort I have no clue: I find it difficult to see
> through which repo contains current gitweb, current repo.or.cz mods, and
> especially the GitBrowser integration bits. Maybe we could ship the
> integration bits without the actual GitBrowser if that is more feasible?

The integration parts are actually present in gitweb, I think. It is a matter of configuration to enable 'graphiclog' link like in http://repo.or.cz

GitBrowser.js is not, I think, the best solution for having graphical history in gitweb, but would do...

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Michael J GruberNext: Michael J Gruber
Message 2 of 4 in “RFD: Shipping GitBrowser.js for instaweb”
  1. Michael J GruberMay 2, 2010
  2. Jakub NarebskiMay 2, 2010
  3. Michael J GruberMay 3, 2010
  4. Jakub NarebskiMay 3, 2010

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.