From: Fred Long <fred_long@fastmail.fm>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
rsbecker@nexbridge.com, git@vger.kernel.org
Subject: Re: git fetch --prune fails with "fatal: bad object"
Date: Wed, 5 Jun 2024 16:43:45 -0700 [thread overview]
Message-ID: <c2a02982-40a9-6629-05c2-c8de3335f35b@fastmail.fm> (raw)
In-Reply-To: <20240605084718.GD2345232@coredump.intra.peff.net>
On 6/5/2024 1:47 AM, Jeff King wrote:
>
> Your local refs should not point to missing objects, though. Each clone
> should maintain its own consistency. Are you using "git clone --shared"
> or another scheme involving alternates?
>
> -Peff
I use Google's "repo" script to manage Android repositories. The "repo"
script runs "git repack -a -d", and I think that's what's removing the
commits locally. Remotely, our bitbucket server removes commits that are
no longer referenced.
next prev parent reply other threads:[~2024-06-05 23:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 22:34 git fetch --prune fails with "fatal: bad object" Curley Joe
2024-05-31 23:27 ` Junio C Hamano
2024-05-31 23:36 ` rsbecker
2024-06-01 15:53 ` Junio C Hamano
2024-06-04 10:44 ` Jeff King
2024-06-04 17:50 ` Junio C Hamano
2024-06-05 8:45 ` Jeff King
2024-06-04 20:09 ` Fred Long
2024-06-05 8:47 ` Jeff King
2024-06-05 23:43 ` Fred Long [this message]
2024-06-06 1:14 ` Jeff King
2024-06-06 20:12 ` Fred Long
2024-06-08 11:20 ` Jeff King
2024-06-08 21:02 ` Fred Long
2024-06-11 7:31 ` Jeff King
2024-06-13 3:29 ` Fred Long
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=c2a02982-40a9-6629-05c2-c8de3335f35b@fastmail.fm \
--to=fred_long@fastmail.fm \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
/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 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 NNTP newsgroup(s).