Possible eGit bug...
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jun 9, 2009, 11:40 UTC
- Message-ID
- <alpine.DEB.1.00.0906091337390.5580@intel-tinevez-2-302>
Hi,
one of my users managed to create 4b825dc trees. In case you do not know what that is: it is a completely empty tree:
$ git hash-object -t tree --stdin < /dev/null
The way he managed to create those trees was by using "git rm --cached" to remove all tracked files from a subdirectory and then committing using eGit.
I have the slight suspicion that eGit is at fault here. Possible? (Sorry, I cannot try myself...)
Ciao, Dscho