Re: I have gone and done a bad thing - malformed tree objects

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 29, 2020, 18:09 UTC
Message-ID: <xmqq8sf2b3be.fsf@gitster.c.googlers.com>
In-Reply-To: <19cab01d66544$ecb402d0$c61c0870$@pdinc.us>

"Jason Pyeron" <jpyeron@pdinc.us> writes:

Show 11 quoted lines

>> gc and fsck may not have pruned the dangling object yet, but
>> --batch-all-objects is a request to enumerate objects that exist in
>> the repository, regardless of their reachability from any ref.
>> 
>> Perhaps "git prune --expire=now" would get rid of it?
>
> Both that and
>
> git -c gc.reflogExpire=now -c gc.reflogExpireUnreachable=now   -c gc.rerereresolved=now -c gc.rerereunresolved=now   -c gc.pruneExpire=now -c gc.worktreePruneExpire=now gc --prune=now --aggressive
>
> leave it in.

If the cruft has already been stored in a packfile, then prune would not touch it. "git repack -a -d && git prune --expire=now" would be the next thing to do.