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

Re: [RFC] gitweb wishlist and TODO list

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Sep 3, 2006, 12:18 UTC
Message-ID
<e5bfff550609030518o5e78bb05w4df4235a4931c2dd@mail.gmail.com>
In-Reply-To
<44fac1ee.308dbbaf.574b.08a5@mx.gmail.com>
>
> By the way, do you known any common Perl modules for generating PNG
> (graphs)?
>

No, I don't. sorry. Anyway, from my experience with qgit I can say that one thing is to produce a revision graph, another thing is to produce a _fast_ and (perhaps more important) no memory hogger revision graph.

Both qgit and gitk implement heavy optimizations and a lot of tricks to make that happen. IMHO this is almost mandatory with long and complex histories like Linux tree. I'm not sure a generic graph builder is up to the task.

More, gitweb is designed to be used by many people at the same time, while qgit and gitk are for personal use only, and this adds burden from the performance/resources point of view.

  Marco
-- 
VGER BF report: U 0.807973
Previous: Jakub NarebskiNext: Jakub Narebski
Message 2 of 3 in “Re: [RFC] gitweb wishlist and TODO list”
  1. Jakub NarebskiSep 3, 2006
  2. Marco CostalbaSep 3, 2006
  3. Jakub NarebskiSep 3, 2006

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.