All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jason Pyeron" <jpyeron@pdinc.us>
Cc: <git@vger.kernel.org>
Subject: Re: I have gone and done a bad thing - malformed tree objects
Date: Wed, 29 Jul 2020 11:09:57 -0700	[thread overview]
Message-ID: <xmqq8sf2b3be.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <19cab01d66544$ecb402d0$c61c0870$@pdinc.us> (Jason Pyeron's message of "Tue, 28 Jul 2020 21:09:35 -0400")

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

>> 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.

  reply	other threads:[~2020-07-29 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  0:47 I have gone and done a bad thing - malformed tree objects Jason Pyeron
2020-07-29  0:52 ` Junio C Hamano
2020-07-29  1:09   ` Jason Pyeron
2020-07-29 18:09     ` Junio C Hamano [this message]
2020-07-31 23:05       ` Jason Pyeron
2020-07-31 23:15         ` Jeff King
2020-08-01  0:01           ` Jason Pyeron
2020-08-01  1:44             ` Jeff King
2020-08-02  2:50               ` Jason Pyeron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8sf2b3be.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jpyeron@pdinc.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.