threads / discuss / 281

fsck-cache problem

Subject: fsck-cache problem

## tl;dr

2 messages between Apr 24, 2005 and Apr 24, 2005.

replies: 1people: 2as markdown or json

Morten Welinder· Apr 24, 2005, 01:55 UTC · lore

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· Apr 24, 2005, 21:24 UTC · re: Morten Welinder · lore

Re: fsck-cache problem

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