{"thread":{"id":"599","subject":"Regarding gitk","startedAt":"2005-05-13T05:19:23Z","lastAt":"2005-05-14T07:47:31Z","messageCount":2,"participants":["Tejun Heo","Paul Mackerras"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"3225","messageId":"20050513051923.GA15116@htj.dyndns.org","threadId":"599","inReplyTo":null,"subject":"Regarding gitk","fromName":"Tejun Heo","fromEmail":"htejun@gmail.com","sentAt":"2005-05-13T05:19:23Z","receivedAt":"2005-05-13T05:19:23Z","isPatch":false,"sender":{"key":"htejun@gmail.com","avatar":null},"body":" Hello, Paulus.\n\n First of all, thanks a lot for gitk.  I was working on something using\ngraphviz/pygtk to do about the same thing for a couple of weeks (and got\npretty far with it) but ditched it as gitk seemed much better.  I really\nlove how gitk shows the commit graph. :-)\n\n As I don't wanna ditch any more of my time, it would be great if you\nlet me know what you're currently working on, so that I can coordinate\nwith you.  Here are the things I have on mind.\n\n* integrate two-way diff view w/ diff map into gitk from mgdiff.\n* show the current cache and working files at the head of graph\n* demand-load commits as the user scrolls down the graph\n\n I wrote a commit viewing utility (gitkdiff) modified from mgdiff two\nweeks ago so I'm quite familiar with mgdiff source, and implemented\ndemand-loading of commits in my own project in python, but writing a\nseparate c utility with the same algorithm wouldn't take that much time.\n\n Thanks.\n\n-- \ntejun\n"},{"id":"3288","messageId":"17029.44307.356844.438027@cargo.ozlabs.ibm.com","threadId":"599","inReplyTo":"20050513051923.GA15116@htj.dyndns.org","subject":"Re: Regarding gitk","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-05-14T07:47:31Z","receivedAt":"2005-05-14T07:47:31Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Hi Tejun,\n\n>  First of all, thanks a lot for gitk.  I was working on something using\n> graphviz/pygtk to do about the same thing for a couple of weeks (and got\n> pretty far with it) but ditched it as gitk seemed much better.  I really\n> love how gitk shows the commit graph. :-)\n\nYes, I was pleased with how it turned out.\n\n>  As I don't wanna ditch any more of my time, it would be great if you\n> let me know what you're currently working on, so that I can coordinate\n> with you.  Here are the things I have on mind.\n> \n> * integrate two-way diff view w/ diff map into gitk from mgdiff.\n\nI guess mgdiff and dirdiff do very similar things, although dirdiff\ncan display the diffs between up to 5 trees (limited mainly by the\nnumber of easily distinguishable colors between red and green).  Doing\n3-way diffs is useful for most merges (diffing the output vs. the\ninputs) and for diffing two arbitrary commits (diffing the two vs. the\nnearest common ancestor).\n\nI recently changed dirdiff to be able to diff git commits with each\nother or the working directory, and I was intending to add a way to\ninvoke that from gitk.\n\n> * show the current cache and working files at the head of graph\n\nInteresting idea.  I had mostly been thinking of gitk in terms of the\nway I use it, which is to help me follow what others are doing rather\nthan looking at what I have done.\n\n> * demand-load commits as the user scrolls down the graph\n\nIt would be nice to at least be a bit asynchronous, so that the graph\nis drawn as the commits are read, rather than having to wait for all\nthe commits are read before anything is drawn.  I need to hack\ngit-rev-tree, I guess.\n\n>  I wrote a commit viewing utility (gitkdiff) modified from mgdiff two\n> weeks ago so I'm quite familiar with mgdiff source, and implemented\n> demand-loading of commits in my own project in python, but writing a\n> separate c utility with the same algorithm wouldn't take that much time.\n\nDoes that algorithm let you say \"commits reachable from A but not from\nB\" like git-rev-tree does?\n\nRegards,\nPaul.\n"}]}