[Monotone-devel] Re: monotone log order

[Bruce Stephens]

Yury Polyanskiy <address@hidden> writes:

[...]

> Ok. Here is my graph. First I created initial revision A and worked on
> the project for a month or so:
>
> A->B->...->R
>
> Now I wanted to import a patch made against original A. So I commited
> that patch and merged and have now this:
>
> A->B->...->R->S
> |             ^  
> \---> A1 -----/

[...]

> Is it ok that _INITIAL_ revision A got between much newer (in dates and
> DAG) R and Q?

Well, maybe not.  

On the other hand, it's hard to see an ordering which would be
obviously right.  It's a graph, not a line, so inevitably serializing
the revisions is going to be annoying sometimes.

Much as I like text tools (especially emacs) this feels like a case
where you really need to draw a graph.  

I don't think any of the tools do this all that well for changelog
browsing: I'd like to see a graph where you can see from the nodes
roughly what their significance is (maybe they could vary in size
depending on the size of the changelog, or depending on the size of
the change (for some definition of size)); and probably the log itself
ought to appear as a popup as you hover your mouse over the nodes.
Maybe not the latter, I'm not sure.