{"thread":{"id":"3968","subject":"new gitk feature","startedAt":"2006-04-26T10:59:29Z","lastAt":"2006-04-28T05:11:14Z","messageCount":5,"participants":["Paul Mackerras","Jan-Benedict Glaw","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19146","messageId":"17487.21137.344427.173131@cargo.ozlabs.ibm.com","threadId":"3968","inReplyTo":null,"subject":"new gitk feature","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2006-04-26T10:59:29Z","receivedAt":"2006-04-26T10:59:29Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"I just pushed some changes to gitk which add a new feature, the\nability to have multiple \"views\" of a repository. Each view is a\nsubgraph of the full graph. At the moment the only subgraph that you\ncan specify is the subgraph containing the commits that affect a\nspecified set of files or directories. You can switch between views\nquickly, and if the currently selected commit exists in the new view\nwhen you switch views, it is selected in the new view. There is one\nview which always exists, the \"All files\" view. If files or\ndirectories are specified on the command line, a \"Command line\" view\nis automatically created and selected at startup.\n\nThus, for the kernel repository I can have a \"PPC\" view which shows\nchanges to arch/powerpc, include/asm-powerpc etc. When looking at a\ncommit in that view, I can switch to the \"All files\" view to see where\nthat commit fits in the overall history.\n\nThere is a \"View\" menu which contains the menu items for creating,\ndeleting, editing and selecting views. If you check the \"Remember\nthis view\" box, gitk will write the definition of the view to your\n~/.gitk file, and it will be automatically put in the list on startup.\n\nI plan to add various other kinds of views, for example, a view that\nshows only the commits that affect a selected file (or part of a file,\nperhaps), and a view that shows just the current commit together with\nall the commits that have tags. (The latter will require some help\nfrom git-rev-list. :)\n\nPaul.\n"},{"id":"19154","messageId":"20060426135735.GQ25520@lug-owl.de","threadId":"3968","inReplyTo":"17487.21137.344427.173131@cargo.ozlabs.ibm.com","subject":"Re: new gitk feature","fromName":"Jan-Benedict Glaw","fromEmail":"jbglaw@lug-owl.de","sentAt":"2006-04-26T13:57:35Z","receivedAt":"2006-04-26T13:57:35Z","isPatch":false,"sender":{"key":"jbglaw@lug-owl.de","avatar":null},"body":"On Wed, 2006-04-26 20:59:29 +1000, Paul Mackerras wrote:\n> Thus, for the kernel repository I can have a \"PPC\" view which shows\n> changes to arch/powerpc, include/asm-powerpc etc. When looking at a\n> commit in that view, I can switch to the \"All files\" view to see where\n> that commit fits in the overall history.\n\nHmm.. Neat feature for arch maintainers. An easy way to see what's\nhappening in the i386 tree for example :)\n\nMfG, JBG\n\n-- \nJan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _\n\"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O\n für einen Freien Staat voll Freier Bürger\" | im Internet! | im Irak! O O O\nret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));\n"},{"id":"19156","messageId":"Pine.LNX.4.64.0604260802050.3701@g5.osdl.org","threadId":"3968","inReplyTo":"17487.21137.344427.173131@cargo.ozlabs.ibm.com","subject":"Re: new gitk feature","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-04-26T15:09:24Z","receivedAt":"2006-04-26T15:09:24Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 26 Apr 2006, Paul Mackerras wrote:\n>\n> I just pushed some changes to gitk which add a new feature, the\n> ability to have multiple \"views\" of a repository. Each view is a\n> subgraph of the full graph. At the moment the only subgraph that you\n> can specify is the subgraph containing the commits that affect a\n> specified set of files or directories. You can switch between views\n> quickly, and if the currently selected commit exists in the new view\n> when you switch views, it is selected in the new view.\n\nThis gets close to something I wanted, but at the same time falls very \nshort of it because the views are always shown completely disjoint.\n\nI've wanted for a long time to have a way to _highlight_ commits. That's \nactually very much a \"view\" thing, but it's a mode where you really see \none view, but the commits that exist in another view have a different \ncolor (or have the commits that _don't_ exist in the other view be grayed \nout).\n\nI hope that your new \"view\" thing would support this notion too: instead \nof having to totally switch between view, it would be wonderful if you \ncould have one \"master view\" and then use another view to \"highlight\".\n\nAlso, I think revision information should be part of a view. For example, \nin the \"highlight\" case, I'd love to have the \"main view\" be the default \n\"everything\", and then have some way to _highlight_ the view that is \ndefined by the revision pattern \"v1.3.1..\"\n\nAny possibility of something light that? I'd _love_ to be able to see the \nwhole tree, but with things that touch certain files or things that are \nnewer highlighted.\n\n(Btw, the \"revision information\" is also cool things like \"--unpacked\". I \nactually use \"gitk --unpacked\" every once in a while, just because it's \nsuch a cool way to say \"show me everything I've added since I packed the \nrepo last).\n\n\t\t\tLinus\n"},{"id":"19204","messageId":"17489.22838.502099.575465@cargo.ozlabs.ibm.com","threadId":"3968","inReplyTo":"Pine.LNX.4.64.0604260802050.3701@g5.osdl.org","subject":"Re: new gitk feature","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2006-04-27T23:52:22Z","receivedAt":"2006-04-27T23:52:22Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Linus Torvalds writes:\n\n> Any possibility of something light that? I'd _love_ to be able to see the \n> whole tree, but with things that touch certain files or things that are \n> newer highlighted.\n\nThat should be quite doable. How about I show the commits that are in\nthe highlight view in bold? That won't conflict with the existing\nyellow background for commits that match the find criteria.\n\n> (Btw, the \"revision information\" is also cool things like \"--unpacked\". I \n> actually use \"gitk --unpacked\" every once in a while, just because it's \n> such a cool way to say \"show me everything I've added since I packed the \n> repo last).\n\nOK, I didn't know about --unpacked. :) I plan to add stuff to the\nview definition window to allow you to select commits to\ninclude/exclude by reachability from given commits (by head/tag/ID)\nand when I do I can add a way to say --unpacked too.\n\nPaul.\n"},{"id":"19215","messageId":"Pine.LNX.4.64.0604272209060.3701@g5.osdl.org","threadId":"3968","inReplyTo":"17489.22838.502099.575465@cargo.ozlabs.ibm.com","subject":"Re: new gitk feature","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-04-28T05:11:14Z","receivedAt":"2006-04-28T05:11:14Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Fri, 28 Apr 2006, Paul Mackerras wrote:\n> Linus Torvalds writes:\n> > Any possibility of something light that? I'd _love_ to be able to see the \n> > whole tree, but with things that touch certain files or things that are \n> > newer highlighted.\n> \n> That should be quite doable. How about I show the commits that are in\n> the highlight view in bold? That won't conflict with the existing\n> yellow background for commits that match the find criteria.\n\nBold sounds good to me.\n\n> > (Btw, the \"revision information\" is also cool things like \"--unpacked\". I \n> > actually use \"gitk --unpacked\" every once in a while, just because it's \n> > such a cool way to say \"show me everything I've added since I packed the \n> > repo last).\n> \n> OK, I didn't know about --unpacked. :) I plan to add stuff to the\n> view definition window to allow you to select commits to\n> include/exclude by reachability from given commits (by head/tag/ID)\n> and when I do I can add a way to say --unpacked too.\n\nIt's more of a gimmick, but I find myself using it occasionally just to \ndecide whether it's time to repack. It falls out automatically - not \nbecause I thought I'd ever want it, but because the --unpacked semantics \nfor git-rev-list are what incremental packing needed.\n\n(Of course, sane people probably just do \"git count-objects\" to decide to \nrepack).\n\n\t\tLinus\n"}]}