# Possible eGit bug...

2 messages from 2009-06-09 to 2009-06-09. Participants: Johannes Schindelin.
Thread: https://gitlist.dev/t/19759

## Johannes Schindelin, 2009-06-09 11:40

Subject: Possible eGit bug...
Message-ID: <alpine.DEB.1.00.0906091337390.5580@intel-tinevez-2-302>
URL: https://gitlist.dev/e/alpine.DEB.1.00.0906091337390.5580%40intel-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

```

## Johannes Schindelin, 2009-06-09 11:42

Subject: Re: Possible eGit bug...
Message-ID: <alpine.DEB.1.00.0906091341480.5580@intel-tinevez-2-302>
URL: https://gitlist.dev/e/alpine.DEB.1.00.0906091341480.5580%40intel-tinevez-2-302
In-Reply-To: <alpine.DEB.1.00.0906091337390.5580@intel-tinevez-2-302>

```
Hi,

On Tue, 9 Jun 2009, Johannes Schindelin wrote:

> 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

```