On Wed, August 17, 2005 2:58 am, Junio C Hamano said: > Paul Mackerras <[EMAIL PROTECTED]> writes: > >> My reasoning is that it is the local short-range connections which are >> interesting and informative. The long-range connections aren't really >> visually informative; if you want to know about the long-range >> connections, the parent and child lists in the details pane are much >> more useful. > > Correct. > > The new output looks a lot less cluttering and I like it very > much, but it is confusing to me on one count. I clicked one > arrowhead pointing downward, expecting that the pane would jump > scroll to show the counterpart arrowhead, and was dissapointed > that it did not happen. I could click the "Parent" link at that > point, but then the upward arrow was above and outside the > visible portion of that pane, which broke visual continuity and > I lost track at that point. I think my being color challenged > exacerbated the resulting confusion; otherwise I could have > probably found the line with the same color as the color of the > downarrow I clicked.
This change looks really good in gitk and clicking on an arrowhead to hop to the corresponding arrowhead would sure be great too. There's may be a way to further reduce the line clutter too; once a line is terminated with an arrowhead, it could often be trimmed back much further. For instance looking at Linus' tree: 03938c3f1062b0f279a0ef937a471d4db83702ed powernow-k8 requires that a data structure for The line flowing from this commit extends ~200 more commits downward before it is finally terminated with an arrowhead. It would be nice if this line could be made shorter, such that the arrowhead was drawn much closer to commit in question. Cheers, Sean - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
