git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / 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: Tue, 28 Jul 2020 17:52:04 -0700	[thread overview]
Message-ID: <xmqqh7trb0sr.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <19ca801d66541$cf872af0$6e9580d0$@pdinc.us> (Jason Pyeron's message of "Tue, 28 Jul 2020 20:47:18 -0400")

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

> I was trying to "do stuff" using hash-object -t tree --stdin -w,
> but I accidentally created trees where other trees were marked as
> blobs. They were dangling and not connected to any actual commits
> on my branches.
>
> After gc and fsck clean ups, everything reports well...
>
> Except:
>
> $ GIT_TRACE=1 git cat-file --batch-all-objects --batch=objecttype

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?

  reply	other threads:[~2020-07-29  0:53 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 [this message]
2020-07-29  1:09   ` Jason Pyeron
2020-07-29 18:09     ` Junio C Hamano
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqh7trb0sr.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).