From: Justin Su <injustsu@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Fetching upstream remote fails if repo was a blobless clone
Date: Sat, 2 Aug 2025 14:28:24 -0400 [thread overview]
Message-ID: <CAB=S_8+aDwMNQkawY-Mod35EDm20mi_=xmmwfngU6As799ppqw@mail.gmail.com> (raw)
In-Reply-To: <CAB=S_8JYbFHJ6WQSyzGO5ns8Fe-NPCdyKjWLmRrsZ1UiZJsReg@mail.gmail.com>
Turns out this was because I had `transfer.fsckObjects = true` in my
global config.
I think you should be able to repro if you change the last command to
`git -c fetch.fsckObjects=true fetch upstream`.
On Sat, Aug 2, 2025 at 2:02 PM Justin Su <injustsu@gmail.com> wrote:
>
> On Sat, Aug 2, 2025 at 5:32 AM Jeff King <peff@peff.net> wrote:
>
> > Is it still happening for you?
>
> Yes, I can still reproduce with that sequence of commands.
next prev parent reply other threads:[~2025-08-02 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 9:30 Fetching upstream remote fails if repo was a blobless clone Justin Su
2025-08-02 9:32 ` Jeff King
2025-08-02 18:02 ` Justin Su
2025-08-02 18:28 ` Justin Su [this message]
2025-08-02 19:31 ` Jeff King
2025-08-02 19:55 ` Jeff King
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='CAB=S_8+aDwMNQkawY-Mod35EDm20mi_=xmmwfngU6As799ppqw@mail.gmail.com' \
--to=injustsu@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).