git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Fetching upstream remote fails if repo was a blobless clone

From
Justin Su <injustsu@gmail.com>
Date
Aug 2, 2025, 18:28 UTC
Message-ID
<CAB=S_8+aDwMNQkawY-Mod35EDm20mi_=xmmwfngU6As799ppqw@mail.gmail.com>
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:
Show 6 quoted lines
>
> 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.
Previous: Justin SuNext: Jeff King
Message 4 of 6 in “Fetching upstream remote fails if repo was a blobless clone”
  1. Justin SuAug 1, 2025
  2. Jeff KingAug 2, 2025
  3. Justin SuAug 2, 2025
  4. Justin SuAug 2, 2025
  5. Jeff KingAug 2, 2025
  6. Jeff KingAug 2, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.