threads / bug / 19759

Possible eGit bug...

Subject: Possible eGit bug...

## tl;dr

2 messages between Jun 9, 2009 and Jun 9, 2009.

replies: 1people: 1as markdown or json

Johannes Schindelin· Jun 9, 2009, 11:40 UTC · lore

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

Johannes Schindelin· Jun 9, 2009, 11:42 UTC · re: Johannes Schindelin · lore

Re: Possible eGit bug...

Hi,

On Tue, 9 Jun 2009, Johannes Schindelin wrote:

Show 8 quoted lines

> 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.

Possibly valuable piece of information: Git is at version 1.5.4.3 there.

Ciao, Dscho