From: "Curley Joe" <m48cv7wg9w@liamekaens.com>
To: git@vger.kernel.org
Subject: git fetch --prune fails with "fatal: bad object"
Date: Fri, 31 May 2024 22:34:42 +0000 [thread overview]
Message-ID: <16919-1717194882-875013@sneakemail.com> (raw)
git fetch --prune fails with "fatal: bad object" for refs that have an invalid sha1 pointer. It would be nice if "git fetch --prune" could prune these refs, because it is a hassle to do it manually. ("git fetch --prune" only shows the first invalid ref, and you have to run "git fsck" and parse it to find the rest.) If it seems like adding this functionality to --prune is a bad idea, then how about adding an option like "--prune-invalid" ?
Thanks.
next reply other threads:[~2024-05-31 22:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 22:34 Curley Joe [this message]
2024-05-31 23:27 ` git fetch --prune fails with "fatal: bad object" 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
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=16919-1717194882-875013@sneakemail.com \
--to=m48cv7wg9w@liamekaens.com \
--cc=git@vger.kernel.org \
/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).