[PATCH 0 of 3] Alternative graph web interface to better handle named branches

[Dirkjan Ochtman]

On Tue, Aug 17, 2010 at 01:22, Francesco Degrassi
<francesco.degrassi at emaze.net> wrote:
> serve/graph: Alternative graph web interface to better handle named branches

Thanks for showing us the code.

> I implemented a new command instead of modifying the "graph" command because:
>  * i thought it to be less invasive to integrate
>  * i suppose someone could prefer the original graph functionality
>  * the code for the backend was almost rewritten, since it has a radically different and complex approach, so there was not much to reuse apart from the upper layers.

Okay, but I don't think we want to graph pages in hgweb. Most of your
features sound like things we'd want for the graph anyway, though. Do
you have the opportunity to help think this through and see if we can
come up with a unified model satisfying all the use cases? In
particular:

* be as simple as possible, but no simpler
* have good performance (currently O(changesets) with fairly low constant)
* work for repos with or without named branches
* have colors that are easily distinguishable for the first 5 or 6 branches

After initially writing the graph support, I haven't been spending
much time on it, so it's definitely overdue for improvement. I wonder
if the THG guys can enlighten us with information on how they do their
graph/what kind of features it supports?

> [web]
> plot_pivot_branches = default, release

Is this the only config option, or are there more?

Cheers,

Dirkjan