From: Fred Long <fred_long@fastmail.fm>
To: "Jeff King peff-at-peff.net |git bugs/Example Allow|"
<y8yky0v9l5xb0yt@sneakemail.com>,
Junio C Hamano <gitster@pobox.com>
Cc: rsbecker@nexbridge.com, git@vger.kernel.org
Subject: Re: git fetch --prune fails with "fatal: bad object"
Date: Tue, 4 Jun 2024 13:09:10 -0700 [thread overview]
Message-ID: <876fbb07-210e-128e-5289-57ab01761750@fastmail.fm> (raw)
In-Reply-To: <20240604104437.GD1781455@coredump.intra.peff.net>
On 6/4/2024 3:44 AM, Jeff King peff-at-peff.net |git bugs/Example Allow|
wrote:
> In the case of a refs/remotes entry where you happen to know that you
> could re-clone from the other side, it is relatively low stakes. But I
> think keeping a human brain in the loop between corruption and deletion
> is a good thing. Corruption should not be happening so often that it's a
> major pain point.
In my case it's not corruption. It's people creating branches, deleting
them, and then removing the commits. (Maybe our git server has an option
to automatically prune commits that are not reachable from a branch or
tag, I don't know.) But this happens very frequently at my work.
next prev parent reply other threads:[~2024-06-04 20:09 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 [this message]
2024-06-05 8:47 ` Jeff King
2024-06-05 23:43 ` Fred Long
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=876fbb07-210e-128e-5289-57ab01761750@fastmail.fm \
--to=fred_long@fastmail.fm \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rsbecker@nexbridge.com \
--cc=y8yky0v9l5xb0yt@sneakemail.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).