# fsck-cache problem

2 messages from 2005-04-24 to 2005-04-24. Participants: Morten Welinder, Linus Torvalds.
Thread: https://gitlist.dev/t/281

## Morten Welinder, 2005-04-24 01:55

Subject: fsck-cache problem
Message-ID: <118833cc0504231855145c10a5@mail.gmail.com>
URL: https://gitlist.dev/e/118833cc0504231855145c10a5%40mail.gmail.com

```
While downloading the sparse git database I got impatient and ran
fsck-cache on it.
I got...

...
missing (null) ff515b91674ff2f5b082a927676dbf392d04d9ce
missing (null) ff94be6fbcce10b83824defbdc2f8819121bbd4d
missing (null) ffa4ddda950185bf313654e903207a3fc2d5f261

That "(null)" is not from git, but from glibc in response to NULL
passed for %s.  It might
as well crash (as some other libc do) or send in the marines.

Morten

```

## Linus Torvalds, 2005-04-24 21:24

Subject: Re: fsck-cache problem
Message-ID: <Pine.LNX.4.58.0504241418270.15879@ppc970.osdl.org>
URL: https://gitlist.dev/e/Pine.LNX.4.58.0504241418270.15879%40ppc970.osdl.org
In-Reply-To: <118833cc0504231855145c10a5@mail.gmail.com>

```


On Sat, 23 Apr 2005, Morten Welinder wrote:
>
> That "(null)" is not from git, but from glibc in response to NULL
> passed for %s. 

Fixed. 

The object library set the types for tree/commit objects only when they
_parsed_ them, resulting in objects that were never parsed (because they
weren't found - because you hadn't gotten them downloaded yet) never
having their type set.

		Linus

```