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

From: Jeff King <peff@peff.net>
Date: Aug 1, 2020, 01:44 UTC
Message-ID: <20200801014443.GA1464485@coredump.intra.peff.net>
In-Reply-To: <046201d66796$fb575bd0$f2061370$@pdinc.us>

On Fri, Jul 31, 2020 at 08:01:58PM -0400, Jason Pyeron wrote:

Show 14 quoted lines

> > That should be dropping everything that isn't reachable. I'd suggest to
> > expire reflogs, though it looks like you've also tried "git gc" with
> > reflog expiration. Does removing .git/logs entirely help?
> > 
> > If not, are you sure it isn't actually reachable from your history? What
> > does:
> > 
> >   git rev-list --all --objects | grep 00009623a06
> 
> $ git rev-list --all --objects | grep 00009623a06
> 00009623a06b8dea7c151542fc789539599c07d0 src/htdocs
> (it is still running...)
> 
> But that is an expected result, I will be back at work on Sunday.

So it sounds like it's still reachable, and you'd need to rewrite history to get rid of it. Or is that object OK, and it's a containing tree that mentions it with the wrong mode the problem? In that case, same question: is the containing tree reachable?

-Peff