[BUG?] gitk assumes initial commit is empty
- From
Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
- Date
- Sep 29, 2011, 14:33 UTC
- Message-ID
- <4E8481A2.6060301@in.waw.pl>
I was looking at gitk display for git itself, and scrolling all the way down to initial commit show this:
Author: Linus Torvalds <torvalds@ppc970.osdl.org> 2005-04-08 00:13:13 Committer: Linus Torvalds <torvalds@ppc970.osdl.org> 2005-04-08 00:13:13 Child: 8bc9a0c769ac1df7820f2dbf8f7b7d64835e3c68 (Add copyright notices.)
Initial revision of "git", the information manager from hell
with no files added or modified. But e.g. 'git show' shows that files were added in the initial commit:
$ git show e83c5163316f89bfbde7d9ab23ca2e25604af290 --stat Author: Linus Torvalds <torvalds@ppc970.osdl.org> Date: Thu Apr 7 15:13:13 2005 -0700 ... 11 files changed, 1244 insertions(+), 0 deletions(-)
In gitk, the next commit shows changes to some files, like if they existed in the parent commit. So it seems that gitk assumes that initial commit is empty, which doesn't have to be true.
This is with gitk from master.
- Zbyszek