{"thread":{"id":"545","subject":"Prototype git commit viewer","startedAt":"2005-05-09T01:40:13Z","lastAt":"2005-05-10T04:54:16Z","messageCount":9,"participants":["Paul Mackerras","Junio C Hamano","Petr Baudis","Benjamin Herrenschmidt","Krzysztof Halasa","Greg KH"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"2850","messageId":"17022.49021.344841.79940@cargo.ozlabs.ibm.com","threadId":"545","inReplyTo":null,"subject":"Prototype git commit viewer","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-05-09T01:40:13Z","receivedAt":"2005-05-09T01:40:13Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Over the weekend I hacked up a prototype viewer for git commits in\nTk. It's called gitk and is at:\n\n\thttp://ozlabs.org/~paulus/gitk\n\n(that's the actual script itself :).\n\nIt displays a window with two panes; the upper one shows a summary of\nall the commits with a graph on the left showing the relationship of\nthe commits (each dot represents a commit, with lines joining parents\nand children). The list is displayed with the most recent commit at\nthe top, and parents below their children.\n\nIf you click on a commit, the bottom pane shows more details of the\ncommit including the commit comments.\n\nI plan to add a pane to show the list of files changed by the commit,\nand provide a way to pop up a dirdiff-style diff viewer window to view\nthe actual diffs. I also plan to add a way to view the diffs between\narbitrary points in the graph using girdiff. There is quite a lot of\nUI tweaking to be done too. However, it's already quite useful in its\ncurrent state.\n\nPaul.\n"},{"id":"2852","messageId":"7vhdhd155x.fsf@assigned-by-dhcp.cox.net","threadId":"545","inReplyTo":"17022.49021.344841.79940@cargo.ozlabs.ibm.com","subject":"Re: Prototype git commit viewer","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-05-09T02:53:14Z","receivedAt":"2005-05-09T02:53:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Good job --- I like it already. Especially the way it correctly\nhandles oddballs like 211232bae64bcc60bbf5d1b5e5b2344c22ed767e\n;-).\n\n\n"},{"id":"2864","messageId":"20050509071341.GA3599@pasky.ji.cz","threadId":"545","inReplyTo":"17022.49021.344841.79940@cargo.ozlabs.ibm.com","subject":"Re: Prototype git commit viewer","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-05-09T07:13:41Z","receivedAt":"2005-05-09T07:13:41Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Mon, May 09, 2005 at 03:40:13AM CEST, I got a letter\nwhere Paul Mackerras told me that...\n> Over the weekend I hacked up a prototype viewer for git commits in\n> Tk. It's called gitk and is at:\n> \n> \thttp://ozlabs.org/~paulus/gitk\n> \n> (that's the actual script itself :).\n> \n> It displays a window with two panes; the upper one shows a summary of\n> all the commits with a graph on the left showing the relationship of\n> the commits (each dot represents a commit, with lines joining parents\n> and children). The list is displayed with the most recent commit at\n> the top, and parents below their children.\n> \n> If you click on a commit, the bottom pane shows more details of the\n> commit including the commit comments.\n> \n> I plan to add a pane to show the list of files changed by the commit,\n> and provide a way to pop up a dirdiff-style diff viewer window to view\n> the actual diffs. I also plan to add a way to view the diffs between\n> arbitrary points in the graph using girdiff. There is quite a lot of\n> UI tweaking to be done too. However, it's already quite useful in its\n> current state.\n\nWhat are its advantages to git-viz?\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"2870","messageId":"1115630723.7339.0.camel@gaston","threadId":"545","inReplyTo":"20050509071341.GA3599@pasky.ji.cz","subject":"Re: Prototype git commit viewer","fromName":"Benjamin Herrenschmidt","fromEmail":"benh@kernel.crashing.org","sentAt":"2005-05-09T09:25:23Z","receivedAt":"2005-05-09T09:25:23Z","isPatch":false,"sender":{"key":"benh@kernel.crashing.org","avatar":null},"body":"\n> \n> What are its advantages to git-viz?\n\nI haven't looked at git-viz in details, but from the screen-shot, I can\nsay I prefer paulus one :)\n\nBut heh, since when should we limit ourselves to a single tool to do a\ngiven job ? :)\n\n\n"},{"id":"2903","messageId":"m3fywwjktf.fsf@defiant.localdomain","threadId":"545","inReplyTo":"17022.49021.344841.79940@cargo.ozlabs.ibm.com","subject":"Re: Prototype git commit viewer","fromName":"Krzysztof Halasa","fromEmail":"khc@pm.waw.pl","sentAt":"2005-05-09T18:50:04Z","receivedAt":"2005-05-09T18:50:04Z","isPatch":false,"sender":{"key":"khc@pm.waw.pl","avatar":null},"body":"Paul Mackerras writes:\n\n> Over the weekend I hacked up a prototype viewer for git commits in\n> Tk. It's called gitk and is at:\n>\n> \thttp://ozlabs.org/~paulus/gitk\n\nNice. I wonder how well would it work with a longer history, say all\nlinux-2.[56] data. It takes gitk ~ 10 seconds to read ~ 1000 Linux\ncommits from cache now, on my system.\n\nIn fact I'm thinking about something working with WWW browser. I've\nwritten a very simple experimental show-tree tool in C and it seems\nreading current Linux tree (no HTTP output yet) takes 0.065s with it.\n\nNow I'm thinking about output language. (X)HTML seems to be not\ncapable (I'm not HTML expert, please correct me if I'm wrong).\n\nAny idea of what can I use?\n\n(will post the source if there is interest)\n-- \nKrzysztof Halasa\n"},{"id":"2915","messageId":"17023.57405.35272.46557@cargo.ozlabs.ibm.com","threadId":"545","inReplyTo":"20050509071341.GA3599@pasky.ji.cz","subject":"Re: Prototype git commit viewer","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-05-09T22:12:13Z","receivedAt":"2005-05-09T22:12:13Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Petr Baudis writes:\n\n> What are its advantages to git-viz?\n\nAs a kernel developer, when I do a pull from Linus' tree, the question\nI want to ask is \"who has been making what changes?\" That's why gitk\nshows the headline and author of each of 30 commits in one screenful.\nAFAICS from the screenshots, git-viz doesn't give me that density of\ninformation (and neither did bk revtool, for that matter).\n\nIt seems to me that git-viz makes the graph topology the primary thing\nand the details of the commits the secondary thing. I want it the\nother way around.\n\nPaul.\n"},{"id":"2926","messageId":"20050510000357.GG15712@pasky.ji.cz","threadId":"545","inReplyTo":"17023.57405.35272.46557@cargo.ozlabs.ibm.com","subject":"Re: Prototype git commit viewer","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-05-10T00:03:57Z","receivedAt":"2005-05-10T00:03:57Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Tue, May 10, 2005 at 12:12:13AM CEST, I got a letter\nwhere Paul Mackerras told me that...\n> Petr Baudis writes:\n> \n> > What are its advantages to git-viz?\n> \n> As a kernel developer, when I do a pull from Linus' tree, the question\n> I want to ask is \"who has been making what changes?\" That's why gitk\n> shows the headline and author of each of 30 commits in one screenful.\n> AFAICS from the screenshots, git-viz doesn't give me that density of\n> information (and neither did bk revtool, for that matter).\n> \n> It seems to me that git-viz makes the graph topology the primary thing\n> and the details of the commits the secondary thing. I want it the\n> other way around.\n\nYes, it looks indeed pretty nice, I have to say after actually looking\nat it.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"2934","messageId":"17024.316.828536.230448@cargo.ozlabs.ibm.com","threadId":"545","inReplyTo":"m3fywwjktf.fsf@defiant.localdomain","subject":"Re: Prototype git commit viewer","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-05-10T00:33:00Z","receivedAt":"2005-05-10T00:33:00Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Krzysztof Halasa writes:\n\n> Nice. I wonder how well would it work with a longer history, say all\n> linux-2.[56] data. It takes gitk ~ 10 seconds to read ~ 1000 Linux\n> commits from cache now, on my system.\n\nAny arguments you give to gitk (other than -b and -d) get passed to\ngit-rev-tree, so you can just look at a section of the tree. (I just\nfixed a bug where it would crash if a commit had a parent that wasn't\nlisted in the git-rev-tree output, so refetch if you want to try it.)\nSo you can do e.g.\n\tgitk 88d7bd8cb9eb8d64bf7997600b0d64f7834047c5 \\\n\t\t^a2755a80f40e5794ddc20e00f781af9d6320fafb\n\nto see all the commits from v2.6.12-rc4 back to but not including\nv2.6.12-rc3 (unfortunately git-rev-tree seems not to cope with being\ngiven tags rather than commit ids).\n\nUltimately I want to add ways to select the range of commits you want\nto look at, e.g. by tags or by dates.\n\nSo as long as git-rev-tree remains fast as the history grows, gitk\nshould remain usable for looking at reasonable-sized chunks of the\nhistory. There are various things I can do to make gitk faster, too,\nup to and including tcl bindings for the core git library. :) \n\n> In fact I'm thinking about something working with WWW browser. I've\n> written a very simple experimental show-tree tool in C and it seems\n> reading current Linux tree (no HTTP output yet) takes 0.065s with it.\n> \n> Now I'm thinking about output language. (X)HTML seems to be not\n> capable (I'm not HTML expert, please correct me if I'm wrong).\n> \n> Any idea of what can I use?\n\nI think I am even less of an HTML expert than you. :)\n\nRegards,\nPaul.\n"},{"id":"2950","messageId":"20050510045415.GA27150@kroah.com","threadId":"545","inReplyTo":"17022.49021.344841.79940@cargo.ozlabs.ibm.com","subject":"Re: Prototype git commit viewer","fromName":"Greg KH","fromEmail":"greg@kroah.com","sentAt":"2005-05-10T04:54:16Z","receivedAt":"2005-05-10T04:54:16Z","isPatch":false,"sender":{"key":"greg@kroah.com","avatar":"https://gravatar.com/avatar/5bb5aa0cc2e01c00ec899d11130c07796bc186e465bae57bc34873b13b72c7c8?d=mp&s=160"},"body":"On Mon, May 09, 2005 at 11:40:13AM +1000, Paul Mackerras wrote:\n> Over the weekend I hacked up a prototype viewer for git commits in\n> Tk. It's called gitk and is at:\n> \n> \thttp://ozlabs.org/~paulus/gitk\n> \n> (that's the actual script itself :).\n\nVery nice, I like it a lot, thanks for doing this.\n\ngreg k-h\n"}]}