{"thread":{"id":"1033","subject":"new features in gitk","startedAt":"2005-06-27T22:22:46Z","lastAt":"2005-06-30T06:20:21Z","messageCount":8,"participants":["Paul Mackerras","Luc Van Oostenryck","Linus Torvalds","Greg KH","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"5308","messageId":"17088.31798.17291.605567@cargo.ozlabs.ibm.com","threadId":"1033","inReplyTo":null,"subject":"new features in gitk","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-06-27T22:22:46Z","receivedAt":"2005-06-27T22:22:46Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"New features that I have added recently to the gitk repository at\n\nrsync://rsync.kernel.org/pub/scm/gitk/gitk.git\n\ninclude:\n\n* Added a right-click context menu on the headlines displayed in the\n  top-left pane with the following entries:\n  - Display diff between two commits\n  - Generate a patch file containing the diff between two commits\n  - Create a local direct tag for a commit\n\n* Left-click on a graph line now displays the parent and the children\n  connected by that line in the bottom-left pane, with buttons\n  allowing you to jump to the parent or a child.\n\n* Pasting into the SHA1 ID field clears it first if it already\n  contains a SHA1 ID.\n\n* Checks for a .git (or $GIT_DIR) directory at startup.\n\nI'm interested to know if people find the diff/patch generation\noptions useful.\n\nPaul.\n"},{"id":"5309","messageId":"42C08265.2050209@looxix.net","threadId":"1033","inReplyTo":"17088.31798.17291.605567@cargo.ozlabs.ibm.com","subject":"Re: new features in gitk","fromName":"Luc Van Oostenryck","fromEmail":"lkml@looxix.net","sentAt":"2005-06-27T22:49:09Z","receivedAt":"2005-06-27T22:49:09Z","isPatch":false,"sender":{"key":"lkml@looxix.net","avatar":null},"body":"Paul Mackerras wrote:\n> \n> I'm interested to know if people find the diff/patch generation\n> options useful.\n> \n> Paul.\n\n\nI find the patch generation very usefull (when I've seen the tool a few days ago, I've said to myself:\n\"what a wonderfull tool, if only I could create a patch from this\")\nbut it doesn't work for me (the first three entries stay always in grey, only the last one \"Create tag\" is in black).\nI'm missing something ?\n\n\nLuc\n"},{"id":"5310","messageId":"17088.36232.479492.643878@cargo.ozlabs.ibm.com","threadId":"1033","inReplyTo":"42C08265.2050209@looxix.net","subject":"Re: new features in gitk","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-06-27T23:36:40Z","receivedAt":"2005-06-27T23:36:40Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Luc Van Oostenryck writes:\n\n> I find the patch generation very usefull (when I've seen the tool a few days ago, I've said to myself:\n> \"what a wonderfull tool, if only I could create a patch from this\")\n> but it doesn't work for me (the first three entries stay always in grey, only the last one \"Create tag\" is in black).\n> I'm missing something ?\n\nThe diffs and patches are between the selected commit (one that you\nclicked on with the left button and which is shown with a grey\nbackground) and the commit where you click the right button.  That was\nthe best way I could think of to indicate which were the two commits\nto diff.  If you (or anyone) has a better suggestion, let me know.\n\nPaul.\n"},{"id":"5312","messageId":"Pine.LNX.4.58.0506271819180.19755@ppc970.osdl.org","threadId":"1033","inReplyTo":"17088.31798.17291.605567@cargo.ozlabs.ibm.com","subject":"Re: new features in gitk","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-06-28T01:21:40Z","receivedAt":"2005-06-28T01:21:40Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Tue, 28 Jun 2005, Paul Mackerras wrote:\n>\n> New features that I have added recently to the gitk repository at\n\nHey, cool, the automatic merge actually worked.\n\nI knew it would, of course, but still.. It's nice when theory and practice \nend up matching.\n\n\t\tLinus\n"},{"id":"5330","messageId":"20050628062256.GA2555@kroah.com","threadId":"1033","inReplyTo":"17088.31798.17291.605567@cargo.ozlabs.ibm.com","subject":"Re: new features in gitk","fromName":"Greg KH","fromEmail":"greg@kroah.com","sentAt":"2005-06-28T06:22:56Z","receivedAt":"2005-06-28T06:22:56Z","isPatch":false,"sender":{"key":"greg@kroah.com","avatar":"https://gravatar.com/avatar/5bb5aa0cc2e01c00ec899d11130c07796bc186e465bae57bc34873b13b72c7c8?d=mp&s=160"},"body":"On Tue, Jun 28, 2005 at 08:22:46AM +1000, Paul Mackerras wrote:\n> I'm interested to know if people find the diff/patch generation\n> options useful.\n\nWell, I find them nice to have, in case I need to generate a real patch.\nNice job.\n\nthanks,\n\ngreg k-h\n"},{"id":"5363","messageId":"42C1B20D.2000502@looxix.net","threadId":"1033","inReplyTo":"17088.36232.479492.643878@cargo.ozlabs.ibm.com","subject":"Re: new features in gitk","fromName":"Luc Van Oostenryck","fromEmail":"lkml@looxix.net","sentAt":"2005-06-28T20:24:45Z","receivedAt":"2005-06-28T20:24:45Z","isPatch":false,"sender":{"key":"lkml@looxix.net","avatar":null},"body":"Paul Mackerras wrote:\n> Luc Van Oostenryck writes:\n> \n> \n>>I find the patch generation very usefull (when I've seen the tool a few days ago, I've said to myself:\n>>\"what a wonderfull tool, if only I could create a patch from this\")\n>>but it doesn't work for me (the first three entries stay always in grey, only the last one \"Create tag\" is in black).\n>>I'm missing something ?\n> \n> \n> The diffs and patches are between the selected commit (one that you\n> clicked on with the left button and which is shown with a grey\n> background) and the commit where you click the right button.  That was\n> the best way I could think of to indicate which were the two commits\n> to diff.  If you (or anyone) has a better suggestion, let me know.\n> \n> Paul.\n\nOK I see it now, it works nicely.\nI didn't found the tric yesterday because I was thinking: one commit -> one patch,\nbut it's probably more usefull like it is now.\n\nThanks.\n"},{"id":"5390","messageId":"17089.57407.401624.981660@cargo.ozlabs.ibm.com","threadId":"1033","inReplyTo":"Pine.LNX.4.58.0506271819180.19755@ppc970.osdl.org","subject":"Re: new features in gitk","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2005-06-28T23:41:51Z","receivedAt":"2005-06-28T23:41:51Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Linus Torvalds writes:\n\n> Hey, cool, the automatic merge actually worked.\n\nYes, very cool.  It'll get more interesting if you make changes to\ngitk in your repository, of course. :)\n\nPaul.\n"},{"id":"5439","messageId":"7vd5q45psq.fsf@assigned-by-dhcp.cox.net","threadId":"1033","inReplyTo":"17088.31798.17291.605567@cargo.ozlabs.ibm.com","subject":"Re: new features in gitk","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-06-30T06:20:21Z","receivedAt":"2005-06-30T06:20:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Finally I started converting my workflow of day-job I do on my\nhome machine from darcs to git, so I started running cvs2git\nover ssh slurping from my office environment (sloooooooooow).\n\nWhile I was watching the import going, I started up gitk on the\nhalfway imported repository, and it showed Japanese characters\nin the source correctly without any special configuration (the\nonly thing I have is LC_CTYPE=ja_JP).  Very often GUIish\nsoftware would not work properly for me with Japanese\ncharacters, and this was a pleasant surprise.\n\nThe credit is probably owed more to tk, not something you do\nspecial in gitk, but nevertheless I am impressed and happy ;-).\n"}]}