{"thread":{"id":"4149","subject":"RE: how to display file history?","startedAt":"2006-05-15T17:24:41Z","lastAt":"2006-05-15T17:54:47Z","messageCount":2,"participants":["Brown, Len","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"20014","messageId":"CFF307C98FEABE47A452B27C06B85BB670FB0A@hdsmsx411.amr.corp.intel.com","threadId":"4149","inReplyTo":null,"subject":"RE: how to display file history?","fromName":"Brown, Len","fromEmail":"len.brown@intel.com","sentAt":"2006-05-15T17:24:41Z","receivedAt":"2006-05-15T17:24:41Z","isPatch":false,"sender":{"key":"len.brown@intel.com","avatar":"https://gravatar.com/avatar/a091f34f66caadb51d85a8a496800c6ccae73737e2f45762373e6b8c55fa5dd6?d=mp&s=160"},"body":">\tgit log --stat -- A\n\nvery handy indeed.\n\nI was surprised on initial use that --stat is\nlimited to the file specified in \"A\" and doesn't\nexpand to describe the entire commit that touches \"A\".\n(ie. the stat output is a subset of what is associated\nwith the displayed commit comments).\n\nThis, of course, is clear now, it just isn't what\nI expected on first use.\n\nthanks,\n-Len\n"},{"id":"20016","messageId":"Pine.LNX.4.64.0605151049470.3866@g5.osdl.org","threadId":"4149","inReplyTo":"CFF307C98FEABE47A452B27C06B85BB670FB0A@hdsmsx411.amr.corp.intel.com","subject":"RE: how to display file history?","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-05-15T17:54:47Z","receivedAt":"2006-05-15T17:54:47Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Mon, 15 May 2006, Brown, Len wrote:\n>\n> >\tgit log --stat -- A\n> \n> very handy indeed.\n> \n> I was surprised on initial use that --stat is\n> limited to the file specified in \"A\" and doesn't\n> expand to describe the entire commit that touches \"A\".\n> (ie. the stat output is a subset of what is associated\n> with the displayed commit comments).\n> \n> This, of course, is clear now, it just isn't what\n> I expected on first use.\n\nWell,  you can obviously have your cake and eat it too (ie \"--full-diff\").\n\nI don't often end up using the \"--full-diff\" thing. It's almost never \nactually worth it until I find the diff that I actually start caring \nabout, and the full diff just makes it harder to see the part I explicitly \ntold git I was interested in.\n\nSo the default \"show only diffs for the files asked for\" behaviour is in \nmy opinion much superior (and it used to be the only one), because the \n\"show the whole thing\" part ends up being something you use only once \nyou've already skimmed the default case and decide to go deeper.\n\nOf course, \"gitk\" ends up using the full diff by default in its diff \nwindow. I'm not convinced that's the right thing, but usually when I use \ngitk I'm primarily looking at the history and the commit messages to \ndecide if it's a relevant one, not the diff, so I don't think it matters.\n\n\t\t\tLinus\n"}]}