{"thread":{"id":"28527","subject":"[BUG?] gitk assumes initial commit is empty","startedAt":"2011-09-29T14:33:06Z","lastAt":"2011-09-29T16:40:27Z","messageCount":2,"participants":["Zbigniew Jędrzejewski-Szmek","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"176487","messageId":"4E8481A2.6060301@in.waw.pl","threadId":"28527","inReplyTo":null,"subject":"[BUG?] gitk assumes initial commit is empty","fromName":"Zbigniew Jędrzejewski-Szmek","fromEmail":"zbyszek@in.waw.pl","sentAt":"2011-09-29T14:33:06Z","receivedAt":"2011-09-29T14:33:06Z","isPatch":false,"sender":{"key":"zbyszek@in.waw.pl","avatar":"https://avatars.githubusercontent.com/u/349618?v=4"},"body":"I was looking at gitk display for git itself, and scrolling all the way\ndown to initial commit show this:\n\nAuthor: Linus Torvalds <torvalds@ppc970.osdl.org>  2005-04-08 00:13:13\nCommitter: Linus Torvalds <torvalds@ppc970.osdl.org>  2005-04-08 00:13:13\nChild:  8bc9a0c769ac1df7820f2dbf8f7b7d64835e3c68 (Add copyright notices.)\n\n    Initial revision of \"git\", the information manager from hell\n\nwith no files added or modified. But e.g. 'git show' shows that files\nwere added in the initial commit:\n\n$ git show e83c5163316f89bfbde7d9ab23ca2e25604af290 --stat\nAuthor: Linus Torvalds <torvalds@ppc970.osdl.org>\nDate:   Thu Apr 7 15:13:13 2005 -0700\n...\n   11 files changed, 1244 insertions(+), 0 deletions(-)\n\nIn gitk, the next commit shows changes to some files, like if they existed\nin the parent commit. So it seems that gitk assumes that initial commit\nis empty, which doesn't have to be true.\n\nThis is with gitk from master.\n\n-\nZbyszek\n"},{"id":"176496","messageId":"7vwrcrti84.fsf@alter.siamese.dyndns.org","threadId":"28527","inReplyTo":"4E8481A2.6060301@in.waw.pl","subject":"Re: [BUG?] gitk assumes initial commit is empty","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-09-29T16:40:27Z","receivedAt":"2011-09-29T16:40:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Zbigniew Jędrzejewski-Szmek  <zbyszek@in.waw.pl> writes:\n\n> In gitk, the next commit shows changes to some files, like if they existed\n> in the parent commit. So it seems that gitk assumes that initial commit\n> is empty, which doesn't have to be true.\n\nIt is not about assuming but by unfortunate design.\n\nIn early days, all projects managed by git (except for git itself) had the\nproduct of a fairly mature development hsitory in their first commit, and\nit was deemed unnecessary clutter to show additions of these thousands of\npaths as a patch.\n\nThis was not just about gitk but git itself. \"git log\" learned to show the\npatch for the initial commit without requiring --root command line option\nonly at 0f03ca9 (config option log.showroot to show the diff of root\ncommits, 2006-11-23).\n\nThese days I think gitk should learn to do the same ;-)\n"}]}